WEBVTT

0:00:08.200000 --> 0:00:13.060000
 Okay, in this section we're going to
 start with an introduction to IPv6.

0:00:13.060000 --> 0:00:18.360000
 I'm not going to be getting on any
 equipment or CLI at this point for

0:00:18.360000 --> 0:00:20.920000
 this first lesson here.

0:00:20.920000 --> 0:00:24.840000
 We're just going to start with some
 basic things you need to know about

0:00:24.840000 --> 0:00:31.760000
 IPv6 before we even really start jumping
 in and configuring it and setting

0:00:31.760000 --> 0:00:35.640000
 it up. So the first question of course,
 which I think at this point most

0:00:35.640000 --> 0:00:40.260000
 people are aware of, but you know,
 why are we even going to IPv6?

0:00:40.260000 --> 0:00:41.960000
 What's the point?

0:00:41.960000 --> 0:00:48.780000
 The first and foremost reason of course
 is that IPv4 only has a maximum

0:00:48.780000 --> 0:00:55.220000
 of 2 to the 32nd IP addresses
 being a 32-bit address.

0:00:55.220000 --> 0:00:59.180000
 And you know, I mean mathematically
 that comes out to right around 3.4

0:00:59.180000 --> 0:01:03.600000
 billion addresses, but hopefully you're
 already aware of the fact that,

0:01:03.600000 --> 0:01:09.640000
 you know, we lose considerable
 amounts of addresses.

0:01:09.640000 --> 0:01:16.080000
 Once you start backing out all your multicast
 addresses, you start backing

0:01:16.080000 --> 0:01:21.640000
 out the entire class A loopback address
 space, not to mention all the

0:01:21.640000 --> 0:01:25.800000
 addresses you lose, simply by the fact
 that we broke it all up into class

0:01:25.800000 --> 0:01:29.360000
 A, class B, class C
 addresses and so on.

0:01:29.360000 --> 0:01:35.200000
 So realistically, there's actually
 far fewer addresses than that.

0:01:35.200000 --> 0:01:40.600000
 But even if we had them all usable,
 we'd still be running out of them

0:01:40.600000 --> 0:01:47.700000
 of course. So here's what
 we're saying here, right?

0:01:47.700000 --> 0:01:49.600000
 That are actually usable.

0:01:49.600000 --> 0:01:55.580000
 Now, if any of you have been in this
 industry for quite some time, you

0:01:55.580000 --> 0:02:04.040000
 may remember back in, oh, I'm going to say
 somewhere in the 95, 1996 timeframe,

0:02:04.040000 --> 0:02:08.720000
 you know, even back then, IANA was yelling,
 you know, we're going to run

0:02:08.720000 --> 0:02:13.060000
 out of address space in IPv4 and of course
 that's when all this all started

0:02:13.060000 --> 0:02:15.060000
 with, you know, and it
 didn't start then.

0:02:15.060000 --> 0:02:17.920000
 I mean, it already under development,
 but you know, this was where the

0:02:17.920000 --> 0:02:21.920000
 whole push sort of for
 IPv6 really started.

0:02:21.920000 --> 0:02:26.160000
 And of course, you know, it's been a long
 time since then sort of regardless

0:02:26.160000 --> 0:02:29.340000
 of when you're listening to this, it's
 been a long time when I'm recording

0:02:29.340000 --> 0:02:33.160000
 it and even longer since you're
 listening to it here.

0:02:33.160000 --> 0:02:37.820000
 But the point is, you know, we've known
 for quite some time that this

0:02:37.820000 --> 0:02:42.600000
 was coming. Now in the meantime, of course,
 they came up with a technology

0:02:42.600000 --> 0:02:46.200000
 called NAT or network
 address translation.

0:02:46.200000 --> 0:02:50.700000
 The idea here I'm sure you're all familiar
 with is that we take a range

0:02:50.700000 --> 0:02:58.060000
 usually from the RFC 1918 address space,
 so our private addresses and

0:02:58.060000 --> 0:03:04.280000
 we enumerate our entire internal network
 with these RFC 1918 addresses

0:03:04.280000 --> 0:03:15.880000
 and then we hide all of those behind
 NAT or if NAT is sort of the more

0:03:15.880000 --> 0:03:17.340000
 generic term for it.

0:03:17.340000 --> 0:03:22.600000
 Everybody calls it that, just generically
 say, oh yeah, we're using NAT.

0:03:22.600000 --> 0:03:27.060000
 The fact of the matter is, I think they're
 probably very, very, very few

0:03:27.060000 --> 0:03:32.160000
 companies and situations
 actually use NAT.

0:03:32.160000 --> 0:03:36.600000
 NAT is a one-to-one translation where
 you would have one public outside

0:03:36.600000 --> 0:03:42.120000
 address for every one internal
 private address.

0:03:42.120000 --> 0:03:45.260000
 Now, that doesn't mean they have to
 be statically mapped, they can still

0:03:45.260000 --> 0:03:49.020000
 be dynamic. So, you know, the way it
 was done is you would have like an

0:03:49.020000 --> 0:03:54.840000
 outside pool, let's say just for an
 example, your company owned, we'll

0:03:54.840000 --> 0:03:58.500000
 just make it simple, we'll say
 a class C address range.

0:03:58.500000 --> 0:04:04.620000
 So let's say you own, you know, essentially
 254 usable addresses and what

0:04:04.620000 --> 0:04:10.200000
 that would mean with NAT is that you
 would have 254 possible hosts inside

0:04:10.200000 --> 0:04:15.240000
 of your network that could access
 the internet at any given time.

0:04:15.240000 --> 0:04:18.620000
 Now, the reason for that, of course,
 is like I said, it's one-to-one.

0:04:18.620000 --> 0:04:22.760000
 For every one internal address that
 tried to go to the outside world,

0:04:22.760000 --> 0:04:26.800000
 it would go through NAT and it would
 be given one of the public addresses

0:04:26.800000 --> 0:04:32.660000
 out of the pool and then all traffic,
 all ports, everything going back

0:04:32.660000 --> 0:04:37.520000
 and forth between that private and
 public address would be translated.

0:04:37.520000 --> 0:04:42.880000
 Now, the obvious problem with this
 is, you know, every machine inside

0:04:42.880000 --> 0:04:47.100000
 talking to the internet needs
 a public outside address.

0:04:47.100000 --> 0:04:51.500000
 When this was first created, you know,
 you have to keep in mind that back

0:04:51.500000 --> 0:04:55.820000
 then not everybody had the internet
 on every machine and not every, you

0:04:55.820000 --> 0:05:01.140000
 know, device inside a company network
 actually needed internet access

0:05:01.140000 --> 0:05:05.440000
 or was even allowed internet
 access or anything else.

0:05:05.440000 --> 0:05:08.980000
 And quite honestly, half the people
 didn't even know what the internet

0:05:08.980000 --> 0:05:15.000000
 was yet. So you have to look at from
 a timeframe perspective, at a certain

0:05:15.000000 --> 0:05:21.140000
 point in time, it would have been no
 problem to have, you know, and of

0:05:21.140000 --> 0:05:24.600000
 course, varied based on company size,
 but, you know, maybe a block of

0:05:24.600000 --> 0:05:30.580000
 16 outside addresses or 32 or maybe
 a whole class C, you know, whatever,

0:05:30.580000 --> 0:05:35.080000
 but you'd have X number of outside
 addresses and then you'd have, you

0:05:35.080000 --> 0:05:41.400000
 know, 200 machines inside the company
 with 16 outside addresses and only

0:05:41.400000 --> 0:05:44.780000
 16 of those machines could
 communicate at once.

0:05:44.780000 --> 0:05:47.060000
 Could you only have
 16 public addresses?

0:05:47.060000 --> 0:05:51.540000
 Now the obvious problem here becomes is
 as the network grows and the internet

0:05:51.540000 --> 0:05:56.780000
 becomes more popular, you know,
 everybody wants internet access.

0:05:56.780000 --> 0:06:00.540000
 You could argue whether they actually
 need it or not inside of a company,

0:06:00.540000 --> 0:06:04.300000
 but regardless, you know, everybody
 had to have internet.

0:06:04.300000 --> 0:06:09.620000
 Well now all of a sudden having 16 out of
 200 machines capable of communicating

0:06:09.620000 --> 0:06:13.700000
 simultaneously just frankly
 wasn't enough.

0:06:13.700000 --> 0:06:18.440000
 So that's where we step up to, of course,
 port address translation where

0:06:18.440000 --> 0:06:25.260000
 we can take, you know, hundreds of machines
 and hide them behind a single

0:06:25.260000 --> 0:06:30.520000
 IPv4 address. So now for your really
 large companies, you could still

0:06:30.520000 --> 0:06:36.880000
 take that block of 16 or, you know,
 250 for addresses, whatever it is

0:06:36.880000 --> 0:06:43.140000
 you have and overload, that's what Cisco
 calls it, other devices honestly

0:06:43.140000 --> 0:06:45.840000
 just refer to it as NAT.

0:06:45.840000 --> 0:06:48.660000
 Cisco refers to it as NAT
 overload on the CLI.

0:06:48.660000 --> 0:06:52.540000
 But at the end of the day we're really
 talking about PAT or port address

0:06:52.540000 --> 0:06:54.740000
 translation. Okay.

0:06:54.740000 --> 0:06:57.740000
 Now all in all what
 does this give us?

0:06:57.740000 --> 0:07:05.060000
 Well, you know, it buys us from 1996
 when, you know, we already started

0:07:05.060000 --> 0:07:08.120000
 throwing up the panic flags, you know,
 holy cow, the internet's growing

0:07:08.120000 --> 0:07:12.460000
 like crazy and they're looking at it,
 looking at the math going, we're

0:07:12.460000 --> 0:07:17.560000
 in big trouble. You know, this cannot
 grow the way we're trying to, to

0:07:17.560000 --> 0:07:24.260000
 really getting us all the way through
 till modern times where we're still

0:07:24.260000 --> 0:07:26.460000
 on IPv4 for the most part.

0:07:26.460000 --> 0:07:30.780000
 Now obviously since you're watching
 this course, we're hoping that, you

0:07:30.780000 --> 0:07:34.500000
 know, you're at least interested in
 IPv6 and learning more about it and

0:07:34.500000 --> 0:07:36.600000
 we are ultimately heading here.

0:07:36.600000 --> 0:07:37.540000
 It's not a question.

0:07:37.540000 --> 0:07:42.180000
 It's not a maybe we're going to, you
 know, someday we will look back on

0:07:42.180000 --> 0:07:46.380000
 this and say, you remember when we used
 to run IPv4, I can't believe anybody

0:07:46.380000 --> 0:07:51.240000
 would still run that anymore, you know,
 you know, how quickly I'm not

0:07:51.240000 --> 0:07:54.640000
 even going to bother trying to
 make a prediction, you know.

0:07:54.640000 --> 0:07:58.120000
 There have been numerous times where
 people have said, oh, it's going

0:07:58.120000 --> 0:07:59.520000
 to happen in two years.

0:07:59.520000 --> 0:08:02.780000
 Yeah. Okay. No. This is going
 to take a long time.

0:08:02.780000 --> 0:08:04.280000
 There's, there's no
 two ways about it.

0:08:04.280000 --> 0:08:06.660000
 We're going to have
 transition phases.

0:08:06.660000 --> 0:08:11.920000
 My personal prediction is that this
 is going to be very, very much like

0:08:11.920000 --> 0:08:18.120000
 if anybody's been around for a while,
 the transition from IPX, SPX to

0:08:18.120000 --> 0:08:20.660000
 IP for a lot of your lands.

0:08:20.660000 --> 0:08:24.660000
 Now some of your big networks started
 off that way and stayed on IP.

0:08:24.660000 --> 0:08:27.680000
 But you know, for people who are running
 no-vell and that where and stuff

0:08:27.680000 --> 0:08:32.600000
 back in the day, it was not an overnight
 translation from one protocol

0:08:32.600000 --> 0:08:41.460000
 to the other. It was a long transition,
 relatively speaking, where we

0:08:41.460000 --> 0:08:44.840000
 were for quite a long time
 running both protocols.

0:08:44.840000 --> 0:08:49.160000
 We would have IPX, SPX running to support
 the land, file and print sharing

0:08:49.160000 --> 0:08:51.540000
 services, that sort of thing.

0:08:51.540000 --> 0:08:57.560000
 And right next to it, running TCP
 IP to support internet access.

0:08:57.560000 --> 0:09:01.820000
 Now obviously things like, you know,
 NetWare and things like that, of

0:09:01.820000 --> 0:09:03.760000
 course, all start
 moving over to IP.

0:09:03.760000 --> 0:09:06.400000
 The need for IPX, SPX goes away.

0:09:06.400000 --> 0:09:10.700000
 And someday, you know, we do that whole
 fateful flip the switch, you know,

0:09:10.700000 --> 0:09:14.020000
 click, okay, IPX, SPX is off.

0:09:14.020000 --> 0:09:16.180000
 Let's see what breaks.

0:09:16.180000 --> 0:09:17.720000
 Hopefully it's not guesswork.

0:09:17.720000 --> 0:09:21.220000
 Hopefully you've done your research
 and you know that nothing else is

0:09:21.220000 --> 0:09:24.580000
 using it. You know, a little bit of
 protocol analysis goes a long way,

0:09:24.580000 --> 0:09:26.980000
 right? But the point is this.

0:09:26.980000 --> 0:09:31.300000
 I think we're going to be doing the
 same thing for a really long time

0:09:31.300000 --> 0:09:37.580000
 with IPV6. You know, a lot of companies
 are just at the point as I'm recording

0:09:37.580000 --> 0:09:41.660000
 this of just starting
 to mess with IPV6.

0:09:41.660000 --> 0:09:42.760000
 Well, let's get it running.

0:09:42.760000 --> 0:09:46.760000
 Let's get it set up and going,
 but we're still really IPV4.

0:09:46.760000 --> 0:09:49.800000
 So it's going to be a long
 drawn out process.

0:09:49.800000 --> 0:09:55.200000
 But the good news is, you know, everything
 is supported with IPV6.

0:09:55.200000 --> 0:09:56.700000
 It's ready to go.

0:09:56.700000 --> 0:10:02.400000
 There's a couple few little things here
 and there that are not supported

0:10:02.400000 --> 0:10:08.280000
 in code, like specifically on Cisco devices
 and such and other manufacturers.

0:10:08.280000 --> 0:10:11.200000
 But it's down to little things.

0:10:11.200000 --> 0:10:16.420000
 You know, when this all started, you
 had basic IPV6 support, but none

0:10:16.420000 --> 0:10:17.240000
 of the fancy features.

0:10:17.240000 --> 0:10:20.060000
 None of the, you know,
 really cool stuff.

0:10:20.060000 --> 0:10:25.420000
 Now we pretty much have everything
 and now it's more the other way.

0:10:25.420000 --> 0:10:28.940000
 Yeah, okay, this little feature here
 is not supported yet or that little

0:10:28.940000 --> 0:10:31.300000
 thing there is not supported yet.

0:10:31.300000 --> 0:10:35.260000
 But it's really come a long way
 since this whole thing started.

0:10:35.260000 --> 0:10:40.820000
 So the other thing, I have one more
 thing on this slide I want to talk

0:10:40.820000 --> 0:10:44.640000
 about, which is the
 whole broadcast.

0:10:44.640000 --> 0:10:49.160000
 You know, layer two, layer three broadcasts
 cause a lot of unnecessary

0:10:49.160000 --> 0:10:53.040000
 CPU load on our end devices.

0:10:53.040000 --> 0:10:56.880000
 Because I mean, the fact of the matter
 is if something's going to a broadcast,

0:10:56.880000 --> 0:11:00.540000
 that means that it's destined
 to you, okay?

0:11:00.540000 --> 0:11:03.140000
 And that's actually one of those things
 I always like to point out to

0:11:03.140000 --> 0:11:05.580000
 people, you know, because you love the
 question, you know, so what does

0:11:05.580000 --> 0:11:09.320000
 a router do with a broadcast?

0:11:09.320000 --> 0:11:13.100000
 And so many times I get the answer because
 I love asking that in classes

0:11:13.100000 --> 0:11:19.100000
 and stuff and all, often hear
 the answer, oh, it drops them.

0:11:19.100000 --> 0:11:23.160000
 And I have to say, well,
 no, no, not specifically.

0:11:23.160000 --> 0:11:27.820000
 If a router dropped broadcasts, then
 rip version one would have had a

0:11:27.820000 --> 0:11:29.740000
 really hard time working.

0:11:29.740000 --> 0:11:34.860000
 Now the fact of the matter is
 the routers don't drop them.

0:11:34.860000 --> 0:11:39.660000
 They don't forward broadcasts or
 they don't route broadcasts.

0:11:39.660000 --> 0:11:41.180000
 However, you want to say that.

0:11:41.180000 --> 0:11:46.960000
 But the point is this, they do
 in fact process broadcasts.

0:11:46.960000 --> 0:11:51.640000
 So just like your end machine does,
 the problem is that every device on

0:11:51.640000 --> 0:11:55.340000
 the segment is in fact the target.


0:11:55.340000 --> 0:11:58.740000
 So if you want to look at it from this
 perspective, why would a router

0:11:58.740000 --> 0:12:02.380000
 forward a broadcast when
 it is the destination?

0:12:02.380000 --> 0:12:06.400000
 That's sort of the point that, you
 know, everybody is the destination

0:12:06.400000 --> 0:12:07.580000
 for the broadcast.

0:12:07.580000 --> 0:12:13.700000
 Now the problem is that packet may
 only be intended for one, two or a

0:12:13.700000 --> 0:12:16.200000
 couple devices on that segment.

0:12:16.200000 --> 0:12:18.960000
 I just use the example
 of rip version one.

0:12:18.960000 --> 0:12:21.800000
 Let's say that you were
 running rip version one.

0:12:21.800000 --> 0:12:24.640000
 I mean, I'm hoping you're not.

0:12:24.640000 --> 0:12:26.620000
 I'm just, you know,
 using an example.

0:12:26.620000 --> 0:12:31.580000
 But let's say you were running rip
 version one between two devices on

0:12:31.580000 --> 0:12:33.460000
 a multi-access land segment.

0:12:33.460000 --> 0:12:34.460000
 So, you know, VLAN.

0:12:34.460000 --> 0:12:38.400000
 On that VLAN, just for the sake of argument,
 you'll say there's a hundred

0:12:38.400000 --> 0:12:39.960000
 machines on there.

0:12:39.960000 --> 0:12:46.980000
 Well every time rip sends out its broadcast
 update every 30 seconds, sending

0:12:46.980000 --> 0:12:51.240000
 out the entire routing table, that means
 that every single device on that

0:12:51.240000 --> 0:12:58.740000
 segment, every PC, Mac, Linux box, everybody
 needs to process that frame.

0:12:58.740000 --> 0:13:00.960000
 Now what they're going to process is
 they're going to get it and they're

0:13:00.960000 --> 0:13:05.660000
 going to bring it up to UDP and they're
 going to look at the port number

0:13:05.660000 --> 0:13:09.580000
 and they're going to say, oh, I'm not
 listening on that UDP port, you

0:13:09.580000 --> 0:13:13.320000
 know. Now depending on the operating
 system, they may or may not realize,

0:13:13.320000 --> 0:13:15.880000
 you know, wait, this is rip.

0:13:15.880000 --> 0:13:16.880000
 I'm not running rip.

0:13:16.880000 --> 0:13:18.380000
 Why am I getting this?

0:13:18.380000 --> 0:13:21.740000
 They may just look at it and go, I'm
 not listening on that port, you know,

0:13:21.740000 --> 0:13:25.680000
 however it works programmatically
 inside is not really important.

0:13:25.680000 --> 0:13:30.880000
 But the fact of the matter is they had
 to interrupt the CPU, take cycles

0:13:30.880000 --> 0:13:35.260000
 to look at this frame to realize,
 hey, this isn't for me.

0:13:35.260000 --> 0:13:41.440000
 Well ultimately, a better thing to do
 would be to throw this frame away

0:13:41.440000 --> 0:13:46.860000
 in hardware. So at the end of the day,
 you know, hopefully we're all running

0:13:46.860000 --> 0:13:49.560000
 switches. I don't even know
 if they make hubs anymore.

0:13:49.560000 --> 0:13:51.660000
 I'm sure somebody does somewhere.

0:13:51.660000 --> 0:13:57.000000
 But, you know, we'll just pretend for a minute
 that we have hubs and everything's

0:13:57.000000 --> 0:13:59.600000
 just one big broadcast
 segment, right?

0:13:59.600000 --> 0:14:01.460000
 One big collision domain.

0:14:01.460000 --> 0:14:10.760000
 You know, the issue becomes even with
 unicast and multicast with a hub

0:14:10.760000 --> 0:14:15.260000
 environment or, you know, just a flat
 out, multi-access segment, everybody

0:14:15.260000 --> 0:14:16.480000
 gets those frames anyway.

0:14:16.480000 --> 0:14:21.440000
 And I think it's sometimes confused people,
 you know, what's the difference

0:14:21.440000 --> 0:14:23.340000
 if there's a hub?

0:14:23.340000 --> 0:14:26.340000
 And the difference honestly all
 comes down to your network card.

0:14:26.340000 --> 0:14:30.940000
 You know, your network card has a burned
-in address from the manufacturer,

0:14:30.940000 --> 0:14:33.900000
 okay? It fits ethernet, which I'm going
 to assume for this course that

0:14:33.900000 --> 0:14:37.120000
 it is. You know, we call
 it a MAC address.

0:14:37.120000 --> 0:14:43.740000
 And the thing is this, if you receive
 that frame and it's not destined

0:14:43.740000 --> 0:14:48.820000
 to your broadcast, or I'm sorry, to your
 MAC address, if it's a broadcast

0:14:48.820000 --> 0:14:53.480000
 or a multicast that you're, and for
 the sake of the multicast, you know,

0:14:53.480000 --> 0:14:55.280000
 you have not joined that group.

0:14:55.280000 --> 0:14:58.420000
 So you're not listening
 for that multicast.

0:14:58.420000 --> 0:15:00.740000
 Your network card,
 we'll look at that.

0:15:00.740000 --> 0:15:06.260000
 It'll look at the destination MAC address
 and it'll say, well, this clearly

0:15:06.260000 --> 0:15:08.180000
 came in on my segment.

0:15:08.180000 --> 0:15:10.960000
 Here it is. Here are the bits
 coming in on the wire.

0:15:10.960000 --> 0:15:15.940000
 But when he looks at the destination
 address and it's not his unicast

0:15:15.940000 --> 0:15:20.280000
 MAC address or any multicast he's listening
 for, he'll just throw that

0:15:20.280000 --> 0:15:25.080000
 away. He just discards it right
 there in hardware at the neck.

0:15:25.080000 --> 0:15:27.160000
 He's not going to bother the CPU.

0:15:27.160000 --> 0:15:29.420000
 He's not going to bother
 the operating system.

0:15:29.420000 --> 0:15:32.140000
 He just says, not for me.

0:15:32.140000 --> 0:15:34.320000
 And I'm going to throw this away.

0:15:34.320000 --> 0:15:37.400000
 So that's, I just want to make sure
 we're clear on the difference of why

0:15:37.400000 --> 0:15:42.840000
 we say that a broadcast creates a CPU
 load, yet multicasts and unicasts

0:15:42.840000 --> 0:15:47.840000
 do not. Now, in the case of most of
 our modern switches, you know, that

0:15:47.840000 --> 0:15:49.960000
 stuff wouldn't happen anyway.

0:15:49.960000 --> 0:15:53.860000
 You know, the first couple of frames
 might, for like an unknown unicast

0:15:53.860000 --> 0:16:00.540000
 or even multicast, if the switch does
 not support IGMP snooping or something

0:16:00.540000 --> 0:16:04.460000
 like that, it is still possible, even
 with today's switches, to get a

0:16:04.460000 --> 0:16:07.940000
 couple of frames or in the case of
 multicast, maybe even a bunch.

0:16:07.940000 --> 0:16:11.400000
 But the fact of the matter is, is your
 network card in hardware will be

0:16:11.400000 --> 0:16:12.840000
 throwing that away.

0:16:12.840000 --> 0:16:15.860000
 Where with a broadcast,
 it can't do that.

0:16:15.860000 --> 0:16:20.240000
 Because again, everybody
 is the destination.

0:16:20.240000 --> 0:16:23.600000
 So the network card looks at that and
 goes, well, it's not my MAC address,

0:16:23.600000 --> 0:16:26.280000
 but it's a broadcast.

0:16:26.280000 --> 0:16:32.240000
 So I'm going to send it on up to the
 CPU because he has to decide whether

0:16:32.240000 --> 0:16:35.440000
 this is for us or not.

0:16:35.440000 --> 0:16:38.360000
 We'll talk more about that in a little
 bit when we get into multicasts

0:16:38.360000 --> 0:16:41.660000
 and the advantages
 that they give us.

0:16:41.660000 --> 0:16:45.500000
 The flip side of that is, of course,
 they bring a little bit of discussion

0:16:45.500000 --> 0:16:49.000000
 to the table. That means
 things have to change.

0:16:49.000000 --> 0:16:51.160000
 So we'll take a look at that here
 in just a second as well.

