3/24/11 Networking Technology for Broadcast Engineers – Part 2 1 Networking Technology for Broadcast Engineers Part 2 March 24, 2011 Wayne M. Pecena, CPBE, 8‐VSB, AMD, DRB, CBNT Texas A&M University Networking Technology for Broadcast Engineers Advertised Presentation Scope: This presentation will provide a Broadcast Focus in major Networking Topics and knowledge of Fundamentals and Principals to equip the Broadcast Engineer with a better knowledge of Fundamentals and Principals to equip the Broadcast Engineer with a better understanding of TCP/IP addresses, Subnetting basics and Subnet Calculation tools, Gateways and the ISO Structure. It will also cover Switching & Routing protocols and fundamentals, MAC Addresses and VLAN fundamentals to provide a base knowledge upon which to build. And, an introduction to IPv6 will present this eminent major change to the whole IP addressing scheme. Goals & Deliverables: What Can You Expect in 2 Hours? ‐ Awareness of Major Networking Topics (broadcast focused) ‐ Basic Understanding of Topic Fundamentals & Principals ‐ Where to Obtain Further Knowledge 2
30
Embed
NetworkingTechnology for Broadcast Engineers · NetworkingTechnology for Broadcast Engineers Part 2 March 24, 2011 ... understanding of TCP/IP addresses, Subnetting basics and Subnet
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
3/24/11
Networking Technology for Broadcast Engineers – Part 2 1
Networking Technology for Broadcast Engineers
Part 2March 24, 2011
Wayne M. Pecena, CPBE, 8‐VSB, AMD, DRB, CBNT
Texas A&M University
Networking Technology for Broadcast Engineers
Advertised Presentation Scope:
This presentation will provide a Broadcast Focus in major Networking Topics and knowledge of Fundamentals and Principals to equip the Broadcast Engineer with a betterknowledge of Fundamentals and Principals to equip the Broadcast Engineer with a better understanding of TCP/IP addresses, Subnetting basics and Subnet Calculation tools, Gateways and the ISO Structure.It will also cover Switching & Routing protocols and fundamentals, MAC Addresses and VLAN fundamentals to provide a base knowledge upon which to build. And, an introduction to IPv6 will present this eminent major change to the whole IP addressing scheme.
Goals & Deliverables:
What Can You Expect in 2 Hours?
‐ Awareness of Major Networking Topics (broadcast focused)‐ Basic Understanding of Topic Fundamentals & Principals‐Where to Obtain Further Knowledge
2
3/24/11
Networking Technology for Broadcast Engineers – Part 2 2
Agenda – Part 2
Review Key Part 1 TakeawaysSubnetting Review
IPv6 FundamentalsWh IP 6a. Why IPv6
b. Addressing Conceptsc. IPv4 to IPv6 Migration Strategies
Switching & Routing Fundamentalsa. Switching Fundamentalsb. MAC Addressesc. VLANSd. Routing Fundamentals & Routing Metricse. Routing Protocolse. Routing Protocolsf. Which Routing Protocol Do I Use?
QoS Basicsa. Why is Quality of Service Needed?b. QoS Typesc. Implementing QoS
Controlling Network Traffic & Security Concerns 3
OSI Model
A Layer Only Interacts With the Layer Below It
4
“All People Seem To Need Data Processing”
A Layer Only Provides Capability for the Layer Above to Interact With It
3/24/11
Networking Technology for Broadcast Engineers – Part 2 3
Encapsulation
5
Ethernet ReviewIEEE 802.3
6
3/24/11
Networking Technology for Broadcast Engineers – Part 2 4
TCP Handshake & Windowing
7
TCP / UDP
TCP ‐ RFC 793
f d “
UDP ‐ RFC 768
“ l ” l• Referred to as a “Connection –Oriented” Protocol
• Guaranteed Or Reliable Data Delivery
– Acknowledgment of Packet Receipt
– Retransmission Occurs if Packet Not Received or Error Occurs
• High Overhead thus Slow
• A “Simple” Protocol or “Lightweight”
• Low Overhead = Fast
• “Best Effort” – Non‐Guaranteed Data Delivery
• Why Use?
– Required for Real‐Time High Overhead thus Slow
• A TCP Conversation Requires Establishment of a 2‐Way “Session” Between Hosts
qApplications ‐ VoIP or Video Transmission”
– Latency More Detrimental Than Data Loss
8
3/24/11
Networking Technology for Broadcast Engineers – Part 2 5
NAT & PAT
NAT PAT
• Translates IP Addresses– Limited IP Address Space
– Security
• Static NAT– 1 to 1 Translation
– Hides Real Host IP Address
• Always Used with NAT
• Allows 65,536 “Inside” Hosts To Be Identified by a Socket Address
• Dynamic NAT (PAT)– 1 to Many Translation
9
IP Address ClassesPublic & Private
• Class A – 126 Networks / 16,777,214 Hosts– 1.0.0.0 to 126.0.0.0
– PRIVATE ‐ 10.0.0.0 to 10.255.255.255
• Class B – 16,384 Networks / 65,534 Hosts– 128.0.0.0 to 191.255.0.0
– PRIVATE ‐ 172.16.0.0 to 172.31.255.255
• Class C – 2,097,152 Networks / 254 Hosts– 192.0.0.0 to 192.255.255.0
– PRIVATE ‐ 192.168.0.0 to 192.168.255.255
10
3/24/11
Networking Technology for Broadcast Engineers – Part 2 6
Private vs Public IP Addresses
• RFC 1918 Established “Private” Address Space– Class A: 10.0.0.0 to 10.255.255.255Class A: 10.0.0.0 to 10.255.255.255
– Class B: 172.16.0.0 to 172.31.255.255
– Class C: 192.168.0.0 to 192.168.255.255
• Key Points:– Private IP Addresses Are NOT Routable Outside the Local Network
– Widely Used in Home & Industry Networks
– May Be Translated With NAT At An Edge Router
• Map Private Address Space to Public Address Space
11
Subnetting
• What is a Subnet?
– Logical Subdivision of a Larger Network– Logical Subdivision of a Larger Network
• Why Do We Subnet?
• Efficient Use of IP Address Space• Efficient Use of IP Address Space
Networking Technology for Broadcast Engineers – Part 2 7
Subnetting Basics
• Identifies the Boundary Between Network and Hosts
• “Subnetting” Simply Moves the Boundary!• Subnetting Simply Moves the Boundary!– Moves Boundary to the Right
– IP Address Subnetting Applies to All Classes
– Boundary Position Determined by the Subnet “Netmask”
• Expressed in Several Forms:– Doted Decimal Notation (same as IP address)
– Slash Notation (also known as CIDR notation)
13
IP Address 165.95.240.100 with Netmask of 255.255.255.0
OR
165.95.240.100 /24
VLSM & CIDR
VLSM ‐ RFC 1009V i bl L h S b M ki (VLSM)
CIDR ‐ RFC 1517, 1518, 1519, 1520
Cl l I d i R i (CIDR)• Variable Length Subnet Masking (VLSM)
– Host Addressing & Routing Inside a Routing Domain
– Allowed “Classless” Subnetting
• Mask Information is Explicit
– Allows More Efficient Use of Address Space
– Allows You to Subnet a Subnet
• Classless Interdomain Routing (CIDR)
– Class System No Longer Applies
– Routing Between Routing Domains
– Class A & B IP Address Exhaustion Pressured Class C Address Space
– Allows “Routing Tables” To Be Reduced by Grouping Contiguous Class C Addresses into One Network
– Allows “Supernets” To Be CreatedAllows Supernets To Be Created
• Combining a Group of Class C Addresses Into a Single Block
– CIDR Notation (slanted notation):172.16.1.1 /16
14
3/24/11
Networking Technology for Broadcast Engineers – Part 2 8
What Must Be KnownAbout a Subnet
IP Address and MaskProvides:Provides:
First Network AddressFirst Network Address Assignable to a HostLast Network Address Assignable to a Host
Broadcast Address
192.0.0.0 /24Provides:
15
Network Address 192.0.0.0First Network Address Assignable to a Host 192.0.0.1Last Network Address Assignable to a Host 192.0.0.254Broadcast Address 192.0.0.255
Number of 232 = 4,294,967,296 2128 = 340,282,366,920,938,463,463,374,607,431,768,211,456Addresses
, , , , , , , , , , , , , , ,
3/24/11
Networking Technology for Broadcast Engineers – Part 2 11
IPv4 Depletion Situation Report
• Each RIR Received Final /8 in February 2011
IANA F P l f IP 4 0%• IANA Free Pool of IPv4 = 0%.
• Each RIR Currently has IPv4 Addresses to Allocate, But Not Forever!
21
Each /8 (Class C) block contains 16,777,216 addresseshttps://www.arin.net/resources/request/ipv4_depletion.html
IPv6 – Is This Adequate Address Space?
• Current Global Demand: – ~24 Million IP Addresses per Month
• IPv6 Address Space:
– Counting /64 subnets it would take ~ 768 Billion years to deplete
– Counting /48 subnets it would take ~ 11.7 Million years to deplete
3/24/11
Networking Technology for Broadcast Engineers – Part 2 12
IPv4 and IPv6 Comparison
• Internet Protocol version 4 (IPv4, or just “IP”)
– First developed for the original Internet (ARPANET) in spring 1978
– Deployed globally with growth of the Internet
– Total of 4 billion IP addresses available
– Well entrenched and used by every ISP and hosting company to connect customers to the Internet
– Allocated based on documented need
• Internet Protocol version 6 (IPv6)
– Design started in 1993 when IETF forecasts showed IPv4 depletion between 2010 and 2017
l l bl f
23
– Completed, tested, and available for production since 1999
– Total of 340,282,366,920,938,463,463,374,607,431,768,211,456 IP addresses available
– Used and managed similar to IPv4
IPv6 Address Format & Notation
128-Bit Address FormatRepresented as a 32 Hexadecimal DigitsRepresented as a 32 Hexadecimal Digits
Subdivided Into Eight Groups of Four Hexadecimal Digits(further summarization may be possible)
2001:0000:0000:0000:0DB8:8000:200C:417Aor
2001:0:0:0:0DB8:8000:200C:417A or
24
or2001::0DB8:8:200C:417A
The Shortest Ipv6 Address:::1
“The Loopback Address”
3/24/11
Networking Technology for Broadcast Engineers – Part 2 13
IPv6 Address Trivia
What Happened to Version 5 of the Internet Protocol?What Happened to Version 5 of the Internet Protocol?
“IPv5 Simply Does Not Exist!
Version 5 was intentionally skipped to avoid confusion, or at least to rectify it. The problem with version 5 relates to an experimental TCP/IP protocol called the Internet Stream Protocol, Version 2, originally defined in RFC 1190. This protocol was originally seen by some as being a peer of IP at the Internet Layer in the TCP/IP architecture and these packets were assigned IP version 5 to differentiate them from
25
architecture and these packets were assigned IP version 5 to differentiate them from “normal” IPv4 packets. This protocol never went anywhere, but to be absolutely sure that there would be no confusion, version 5 was skipped over in favor of version 6.”
The Environment Today
• The Industry is Predominantly IPv4 Based Today
• IPv4 Demand Continues…..
• IPv4 Availability Pool Rapidly Decreasing
• IPv4 NAT Use Increasing
• IPv6 Must Be Adopted for Continued Growth
• IPv6 is NOT Backward Compatible With IPv4
• IPv4 and IPv6 Must BOTH Be Maintained for Many Years to Come – “Dual‐Stack Approach”
26
My IPv4 Address: 128.194.247.55
My IPv6 Address: 2002:80c2:f737::80c2:f737
My MAC Address: 80:C2:F7:37
3/24/11
Networking Technology for Broadcast Engineers – Part 2 14
An Approach
• Call to Action – Enterprise Networks– IPv6 Enable Web, Mail, and Public‐Facing Application Servers
– Open Dialog With Your ISP Regarding IPv6 Connectivity Availability & Options
• Call to Action – Content Providers– You Must Be Reachable By New Internet Customers
– Provide IPv4 and IPv6 Connectivity Today
– If Only IPv4 Content is Provided – You Reachability is Determined by Access Provider Transition Solutions
IPv6 Implementation
• Technology Areas of Focus:
– Obtain IPv6 Address Spacep
– Obtain IPv6 Connectivity
• Native
• Tunneled
– Upgrade / Configure Operating Systems
– Upgrade / Configure Routers, Firewalls, DNS
28
3/24/11
Networking Technology for Broadcast Engineers – Part 2 15
IPv6 Connectivity
29
World IPv6 DayJune 8, 2011
30
http://isoc.org/wp/worldipv6day/
3/24/11
Networking Technology for Broadcast Engineers – Part 2 16
Takeaways
• IPv6 Awareness– More Than Expanded Address SpaceMore Than Expanded Address Space
• IPv6 Address Format & Notation– 128 Bit Number Hexadecimal Number
– Nomenclature ‐ Eight Groups of Four Hexadecimal Digits
• Develop Plans for IPv4 / IPv6 Especially if a Content Provider– Upstream Provider IPv6 Availability?
• NativeNative
• Tunneled
• IPv4 and IPv6 Will Co‐Exist in The Foreseeable Future
31
Switching Fundamentals
• Legacy Ethernet Used Hubs– An “Ethernet DA” of sorts – All Bits Go to All Ports
– High Collision Level Due to Shared Media(40‐50% of Bandwidth Consumed by Collision Recovery)
– High Collision Level Yields High Latency
• Switches Allow Segmentation of Network– Allows Dedicated Bandwidth and Point‐Point Communications
– Increased Throughput Due to Zero or Minimal Collisions