PK o\_rels/PK o\ docProps/PK o\ppt/PK o\ ppt/_rels/PK o\ ppt/charts/PK o\ppt/charts/_rels/PK o\ppt/embeddings/PK o\ ppt/media/PK o\ppt/slideLayouts/PK o\ppt/slideLayouts/_rels/PK o\ppt/slideMasters/PK o\ppt/slideMasters/_rels/PK o\ ppt/slides/PK o\ppt/slides/_rels/PK o\ ppt/theme/PK o\ppt/notesMasters/PK o\ppt/notesMasters/_rels/PK o\ppt/notesSlides/PK o\ppt/notesSlides/_rels/PK o\ }"}"[Content_Types].xml PK o\]] _rels/.rels PK o\ȳdocProps/app.xml 0 0 Microsoft Office PowerPoint On-screen Show (16:9) 0 16 16 0 0 false Fonts Used 2 Theme 1 Slide Titles 16 Arial Calibri Office Theme Slide 1Slide 2Slide 3Slide 4Slide 5Slide 6Slide 7Slide 8Slide 9Slide 10Slide 11Slide 12Slide 13Slide 14Slide 15Slide 16 PptxGenJS false false false 16.0000 PK o\zZ(docProps/core.xml OSI Model — Complete Guide PptxGenJS Presentation PptxGenJS PptxGenJS 1 2026-04-06T00:11:31Z 2026-04-06T00:11:31Z PK o\]rF F ppt/_rels/presentation.xml.rels PK o\Oݨ ppt/theme/theme1.xmlPK o\͙ppt/presentation.xml PK o\Xppt/presProps.xml PK o\ppt/tableStyles.xml PK o\D >00ppt/viewProps.xml PK o\H7t!ppt/slideLayouts/slideLayout1.xml PK o\ђ77,ppt/slideLayouts/_rels/slideLayout1.xml.rels PK o\MeѢ))ppt/slides/slide1.xml OSI ModelOpen Systems Interconnection — How Data Travels Across a Network7 LayersProtocolsReal ExamplesWiresharkMnemonic: All People Seem To Need Data Processing (Layer 7 down to Layer 1)See every OSI layer LIVE using Wireshark!PK o\3 ppt/slides/_rels/slide1.xml.rels PK o\.ppt/notesSlides/notesSlide1.xml 1PK o\:A*ppt/notesSlides/_rels/notesSlide1.xml.rels PK o\ -2-2ppt/slides/slide2.xml OSI Model — Why Should You Learn This? 🌐A Universal LanguageIT professionals worldwide use the OSI model as a shared language. When someone says 'Layer 3 problem' — every engineer immediately knows what it means. Switch issue? Layer 2. IP not routing? Layer 3. This common framework works across companies, countries, and technologies. 🔍A Troubleshooting FrameworkWhen your network breaks, you don't randomly restart things. Start at Layer 1 — is the cable plugged in? Is the signal strong? Work your way up layer by layer until you find where the problem is. This is how professionals debug networks systematically. 📡Protocol OrganizationEvery protocol maps to a specific OSI layer. HTTP = Layer 7, TLS = Layer 6, TCP = Layer 4, IP = Layer 3, Ethernet = Layer 2, Cables = Layer 1. Once you understand this mapping, every networking concept starts clicking into place.OSI = Open Systems Interconnection | Developed by ISO in 1984PK o\2- ppt/slides/_rels/slide2.xml.rels PK o\ppt/notesSlides/notesSlide2.xml 2PK o\xշ*ppt/notesSlides/_rels/notesSlide2.xml.rels PK o\׆׆ppt/slides/slide3.xml 7 Layers at a GlanceAll People Seem To Need Data Processing7ApplicationHTTP, FTP, DNS, SMTPAllL7 Firewall6PresentationSSL/TLS, JPEG, MP4, ASCIIPeople—5SessionNetBIOS, RPC, PPTPSeem—4TransportTCP, UDP, Port NumbersTo—3NetworkIP, ICMP, ARP, BGPNeedRouter2Data LinkEthernet 802.3, Wi-Fi 802.11DataSwitch, AP1PhysicalCables, Hubs, Bits, SignalsProcessingHub, NICPK o\W/ ppt/slides/_rels/slide3.xml.rels PK o\K |Őppt/notesSlides/notesSlide3.xml 3PK o\9 Y*ppt/notesSlides/_rels/notesSlide3.xml.rels PK o\QQppt/slides/slide4.xml Layer 7 — Application Layer"All" What does this layer do?The Application Layer is the interface between the user and the network. When you open a browser and type a URL, send an email, or transfer a file — the Application Layer is at work. It provides network services directly to end-user applications and prepares data for transmission. Protocols & TechnologiesHTTP (Port 80) — Loading websites in your browserHTTPS (Port 443) — Secure, encrypted websitesFTP (Port 21) — File transfer between systemsDNS (Port 53) — Translating domain names to IP addressesSMTP (Port 25) — Sending emailsSSH (Port 22) — Secure remote server accessTelnet (Port 23) — Remote access (unencrypted, outdated) Network DeviceLayer 7 Firewall — Performs Deep Packet Inspection on application data Real World ExampleYou type google.com in Chrome. The browser builds an HTTP GET request — this happens at Layer 7. The request then travels down through each lower layer before hitting the network. Wireshark FilterIn Wireshark: type 'http' or 'dns' in the filter bar. You will see all HTTP requests and DNS queries with full headers, URLs, and status codes.Remember: User interacts directly = Layer 7. Key ports: 80, 443, 21, 22, 25, 53Layer 7: Application | OSI ModelPK o\` ppt/slides/_rels/slide4.xml.rels PK o\vsppt/notesSlides/notesSlide4.xml 4PK o\J *ppt/notesSlides/_rels/notesSlide4.xml.rels PK o\|$OOppt/slides/slide5.xml Layer 6 — Presentation Layer"People" What does this layer do?The Presentation Layer acts as a translator. It ensures data is in a format the receiving application can understand. It handles three key tasks: data format translation (e.g. JPEG to PNG), encryption and decryption (SSL/TLS), and compression to reduce the size of data before transmission. Protocols & TechnologiesSSL/TLS — Encrypts data for HTTPS connectionsJPEG, PNG, GIF — Standard image formatsMP4, H.264 — Video compression standardsASCII, Unicode — Text encoding standardsEBCDIC — Text encoding for IBM mainframe systemsMIME — Encoding for email attachments Network DeviceNo dedicated hardware — Handled by software, OS, and applications Real World ExampleWhen you log into your bank website over HTTPS, TLS encryption happens at Layer 6. Your password is encrypted here before it ever leaves your device. The server decrypts it at Layer 6 on their end. Wireshark FilterIn Wireshark: type 'tls' in the filter bar. Watch the TLS handshake — Client Hello, Server Hello, Certificate exchange — this is Layer 6 encryption being set up in real time.Remember: Encryption, compression, or data format conversion = Layer 6. TLS/SSL = Layer 6.Layer 6: Presentation | OSI ModelPK o\5 ppt/slides/_rels/slide5.xml.rels PK o\W8ppt/notesSlides/notesSlide5.xml 5PK o\Qe*ppt/notesSlides/_rels/notesSlide5.xml.rels PK o\OOppt/slides/slide6.xml Layer 5 — Session Layer"Seem" What does this layer do?The Session Layer manages conversations between two devices. It is responsible for establishing a session, maintaining it while data is being exchanged, and terminating it gracefully when the communication ends. If a connection drops mid-session, Layer 5 can attempt to resume it. Protocols & TechnologiesNetBIOS — Session management for Windows networksRPC (Remote Procedure Call) — Execute code on a remote computerSIP — Setup and teardown of voice and video calls (VoIP)PPTP — VPN tunneling protocolH.245 — Multimedia conference call controlNFS — Network File System session management Network DeviceNo dedicated hardware — Managed by application-layer software and the OS Real World ExampleWhen you make a Zoom call: the call starting is session establishment, staying connected while you talk is session maintenance, and hanging up is session termination. That entire lifecycle is Layer 5. Wireshark FilterIn Wireshark: type 'sip' in the filter bar. You will see SIP INVITE, 200 OK, and BYE messages — these are the session setup and teardown messages for a VoIP call.Remember: Connection start, maintain, or end = Layer 5. Video calls, RPC, VoIP = Layer 5.Layer 5: Session | OSI ModelPK o\ج+ ppt/slides/_rels/slide6.xml.rels PK o\zppt/notesSlides/notesSlide6.xml 6PK o\=|*ppt/notesSlides/_rels/notesSlide6.xml.rels PK o\13QQppt/slides/slide7.xml Layer 4 — Transport Layer"To" What does this layer do?The Transport Layer delivers data end-to-end between source and destination. It segments large data into smaller chunks, sends them, and reassembles them in the correct order at the destination. The two core protocols are TCP (reliable) and UDP (fast). Port numbers also live at this layer. Protocols & TechnologiesTCP — Reliable, connection-oriented, uses acknowledgementsUDP — Fast, connectionless, no delivery guaranteePort Numbers — 0-1023 well-known, 1024-49151 registeredTCP 3-Way Handshake — SYN, SYN-ACK, ACKFlow Control — Manages the speed of data transmissionError Detection — Checksum to detect corrupted dataSegmentation — Splits large data into smaller segments Network DeviceNo hardware device — Handled by the OS networking stack Real World ExampleDownloading a file uses TCP — every packet is acknowledged, and lost packets are resent. YouTube streaming uses UDP — if a frame is lost, the video just keeps playing. Speed matters more than perfection for streaming. Wireshark FilterIn Wireshark: type 'tcp' and find the 3-way handshake — SYN, SYN-ACK, ACK. Type 'udp' to see UDP traffic. Port numbers are visible in every packet.Remember: TCP vs UDP = Layer 4. Port numbers = Layer 4. Segmentation = Layer 4.Layer 4: Transport | OSI ModelPK o\F ppt/slides/_rels/slide7.xml.rels PK o\)lppt/notesSlides/notesSlide7.xml 7PK o\|g*ppt/notesSlides/_rels/notesSlide7.xml.rels PK o\0QQppt/slides/slide8.xml Layer 3 — Network Layer"Need" What does this layer do?The Network Layer routes data from one network to another using IP addresses. Routers operate at this layer. Each router only knows the next hop — but by passing the packet from router to router, data can travel from your laptop in one country to a server on the other side of the world. Protocols & TechnologiesIPv4 — 32-bit addresses (e.g. 192.168.1.1)IPv6 — 128-bit addresses (future-proof, e.g. 2001:db8::1)ICMP — Error messages and the ping utilityARP — Maps IP addresses to MAC addressesOSPF, BGP, RIP — Routing protocols for path selectionNAT — Translates private IPs to public IPsTTL — Time To Live, prevents infinite routing loops Network DeviceRouter — the Layer 3 device. Layer 3 Switches also possible. Real World ExampleRun 'ping google.com' in your terminal. An ICMP packet travels at Layer 3 from your router to your ISP to Google — each hop checking the destination IP. Run 'traceroute google.com' to see every router along the path. Wireshark FilterIn Wireshark: type 'icmp' to see ping packets. Type 'ip.addr == 8.8.8.8' to filter traffic to/from Google DNS. See source IP, destination IP, and TTL in every packet.Remember: IP address = Layer 3. Router = Layer 3 device. ping uses ICMP = Layer 3.Layer 3: Network | OSI ModelPK o\6 ppt/slides/_rels/slide8.xml.rels PK o\iސppt/notesSlides/notesSlide8.xml 8PK o\pO*ppt/notesSlides/_rels/notesSlide8.xml.rels PK o\%l`'CRCRppt/slides/slide9.xml Layer 2 — Data Link Layer"Data" What does this layer do?The Data Link Layer handles communication within a single network using MAC addresses. While Layer 3 routes between networks, Layer 2 delivers frames within the same LAN. Switches operate here — they maintain a MAC address table and send frames only to the correct destination port. Protocols & TechnologiesEthernet (IEEE 802.3) — The standard for wired LANWi-Fi (IEEE 802.11) — The standard for wireless LANMAC Addresses — 48-bit hardware addresses (e.g. AA:BB:CC:DD:EE:FF)ARP — Resolves IP addresses to MAC addressesPPP — Point-to-Point Protocol for direct connectionsVLAN (802.1Q) — Virtual LANs on shared physical infrastructureSTP — Spanning Tree Protocol, prevents switching loops Network DeviceSwitch (Layer 2) — forwards frames by MAC address. Access Point (Layer 2 bridge). Real World ExampleYour laptop sends a packet to the switch. The switch checks its MAC address table and sends the frame only to the correct port — just to the destination device, not broadcast to everyone. That selective forwarding is Layer 2. Wireshark FilterIn Wireshark: type 'eth' to see Ethernet frames with source and destination MAC addresses. Type 'arp' to see ARP requests — your device asking 'Who has this IP address? Tell me your MAC!'Remember: MAC address = Layer 2. Switch = Layer 2. Ethernet/Wi-Fi = Layer 2. Frame = L2 PDU.Layer 2: Data Link | OSI ModelPK o\>$ ppt/slides/_rels/slide9.xml.rels PK o\qppt/notesSlides/notesSlide9.xml 9PK o\1*ppt/notesSlides/_rels/notesSlide9.xml.rels PK o\ )|R|Rppt/slides/slide10.xml Layer 1 — Physical Layer"Processing" What does this layer do?The Physical Layer is the actual physical medium — copper cables, fiber optic cables, or wireless radio signals. At this layer there is no addressing, no error correction, and no protocols. Just raw bits — zeros and ones — converted into electrical signals, pulses of light, or radio waves and sent across the medium. Protocols & TechnologiesEthernet cables — Cat5e (up to 1 Gbps), Cat6 (up to 10 Gbps)Fiber Optic — Single mode (long distance), Multi mode (short distance)Wi-Fi signals — 2.4 GHz, 5 GHz, and 6 GHz frequency bandsBit rate — Number of bits transmitted per secondConnectors — RJ-45, LC, SC, SFP transceiversHubs — Broadcast all signals to every port (Layer 1 device)NIC — Network Interface Card, sends and receives bits Network DeviceHub (Layer 1 — broadcasts to all ports). Cables, Repeaters, NICs, Modems. Real World ExampleYour internet is slow. Start troubleshooting at Layer 1 — is the cable damaged or loose? Is your Cat5e cable limiting you to 100Mbps when you need 1Gbps? Is your Wi-Fi signal weak because you are too far from the router? Physical issues are always checked first. Wireshark FilterWireshark starts at Layer 2 — Layer 1 itself is not directly visible. However, frequent CRC errors or malformed frames in Wireshark often indicate an underlying Layer 1 physical problem.Remember: Cable, signal, NIC, Hub = Layer 1. Physical troubleshooting always starts at Layer 1!Layer 1: Physical | OSI ModelPK o\Ѳ!ppt/slides/_rels/slide10.xml.rels PK o\O ppt/notesSlides/notesSlide10.xml 10PK o\T+ppt/notesSlides/_rels/notesSlide10.xml.rels PK o\>QIIppt/slides/slide11.xml Wireshark — See Live Network Traffic on Your Screen What is Wireshark?Wireshark is a free, open-source network protocol analyzer. It captures every packet passing through your network interface and lets you inspect it in detail. You can see OSI layers 2 through 7 in real time — watching data actually travel across the network. Installation — Step by Step1. Go to wireshark.org and click Download2. Download the Windows Installer (.exe)3. During install — make sure to install Npcap or WinPcap (required for packet capture)4. On Kali Linux: sudo apt install wireshark5. On Kali: sudo usermod -aG wireshark $USER (then log out and back in) Wireshark: 3 PanelsPanel 1 — Packet ListTop section: Every captured packet as a row. Shows time, source IP, destination IP, protocol, and info.Panel 2 — Packet DetailsMiddle section: The selected packet broken down layer by layer. Expand each layer to see OSI in action.Panel 3 — Packet BytesBottom section: Raw hex and ASCII bytes — the actual data that traveled across the cable.Download: wireshark.orgWireshark — Free & Open Source Network Analyzer | wireshark.orgPK o\;!ppt/slides/_rels/slide11.xml.rels PK o\s6ӑ ppt/notesSlides/notesSlide11.xml 11PK o\O+ppt/notesSlides/_rels/notesSlide11.xml.rels PK o\#ppt/slides/slide12.xml Wireshark — See Each OSI Layer Live Start capturing: Select your interface (Wi-Fi or eth0) → Click the green Shark button → Traffic will start flooding in immediatelyLayer 7httpWebsite traffic — see HTTP requests and responses, GET/POST methods, URLs, status codes like 200 OK or 404 Not FoundLayer 7dnsDNS queries — see which domain resolved to which IP address. Both the question and answer are shownLayer 6tlsTLS handshake — the encryption setup process. Client Hello, Server Hello, Certificate, FinishedLayer 4tcpTCP connections — find the 3-way handshake (SYN, SYN-ACK, ACK). Port numbers clearly visible on every packetLayer 4udpUDP packets — connectionless and fast. DNS, DHCP, video streaming all use UDPLayer 3icmpPing traffic — ICMP Echo Request and Echo Reply. TTL and IP headers clearly visibleLayer 3ip.addr == 8.8.8.8Filter only traffic to/from Google DNS. Replace 8.8.8.8 with any IP address to isolate specific trafficLayer 2arpARP requests — your device broadcasting to find the MAC address for a given IP. Network discovery in actionType any filter in the Wireshark filter bar and press Enter — live traffic filtered instantlyPK o\c!ppt/slides/_rels/slide12.xml.rels PK o\*)@ ppt/notesSlides/notesSlide12.xml 12PK o\Fb+ppt/notesSlides/_rels/notesSlide12.xml.rels PK o\^^ppt/slides/slide13.xml Wireshark — Practical Exercise: Trace Every OSI Layer Exercise: Capture a real HTTP request and identify every OSI layer inside a single packet 1Start CapturingOpen Wireshark → Select your interface (Wi-Fi or eth0) → Click the green button → Capture starts 2Open http://example.com in BrowserUse HTTP (not HTTPS) so we can see unencrypted data. Type the URL and press Enter 3Filter: httpType "http" in the Wireshark filter bar. Find the HTTP GET request row and click on it 4Expand the Packet Details PanelIn the middle panel, expand each section — Frame → Ethernet → IP → TCP → HTTP (every OSI layer!) 5Note What Each Layer ShowsL1: Frame bytes | L2: MAC addresses | L3: IP src/dst | L4: TCP ports | L7: HTTP GET / 6Follow TCP StreamRight-click the packet → Follow → TCP Stream. See the full conversation — your request and the server responseAfter this exercise, the OSI model will make complete sense — you will see it working live!PK o\x!ppt/slides/_rels/slide13.xml.rels PK o\Ї ppt/notesSlides/notesSlide13.xml 13PK o\yv+ppt/notesSlides/_rels/notesSlide13.xml.rels PK o\uрIIppt/slides/slide14.xml Data Encapsulation — What Each Layer Adds When sending data: Top to bottom — each layer adds its own header (Encapsulation). When receiving: Bottom to top — each layer reads and removes its header (De-encapsulation).L7 — Data+ HTTP headers, application dataL6 — Data+ Encryption / format conversion (TLS)L5 — Data+ Session tokens, connection identifiersL4 — Segment+ TCP/UDP header: src port, dst port, seq#L3 — Packet+ IP header: source IP, destination IP, TTLL2 — Frame+ Ethernet header: src MAC, dst MAC + FCSL1 — Bits+ Physical signal: electrical / light / radioHeader Added →PDU Names: L7-L5 = Data | L4 = Segment | L3 = Packet | L2 = Frame | L1 = BitsPK o\O!ppt/slides/_rels/slide14.xml.rels PK o\0 ppt/notesSlides/notesSlide14.xml 14PK o\?ݤ+ppt/notesSlides/_rels/notesSlide14.xml.rels PK o\8=ppt/slides/slide15.xml Quick Reference — Complete Revision CardLayerNameProtocolsDeviceMnemonicWireshark7ApplicationHTTP/HTTPS, FTP, DNS, SMTP, SSHL7 FirewallAllhttp, dns6PresentationSSL/TLS, JPEG, MP4, ASCII—Peopletls, ssl5SessionNetBIOS, RPC, SIP, NFS—Seemsip4TransportTCP, UDP, Port Numbers—Totcp, udp3NetworkIP, ICMP, ARP, BGPRouterNeedicmp, ip2Data LinkEthernet 802.3, Wi-Fi 802.11, MACSwitch, APDataarp, eth1PhysicalCables, Hubs, NIC, Bits, SignalsHub, NICProcessing—All People Seem To Need Data Processing — (Layer 7 down to Layer 1)PK o\*R!ppt/slides/_rels/slide15.xml.rels PK o\Qz ppt/notesSlides/notesSlide15.xml 15PK o\$Q+ppt/notesSlides/_rels/notesSlide15.xml.rels PK o\Jf--ppt/slides/slide16.xml SummaryKey Takeaways — OSI ModelThe OSI Model has 7 layers — from Layer 1 (Physical) up to Layer 7 (Application)Mnemonic: All People Seem To Need Data Processing — Layer 7 down to Layer 1Router = Layer 3 | Switch = Layer 2 | Hub = Layer 1TCP/UDP = Layer 4 | IP address = Layer 3 | MAC address = Layer 2Use Wireshark to see every layer live — best way to truly understand networkingWhen troubleshooting — always start at Layer 1 and work your way upNext Topic: Networking Devices — Switches, Routers, Firewalls, Access Points →PK o\ !ppt/slides/_rels/slide16.xml.rels PK o\  ppt/notesSlides/notesSlide16.xml 16PK o\ y+ppt/notesSlides/_rels/notesSlide16.xml.rels PK o\K !ppt/slideMasters/slideMaster1.xml PK o\N),ppt/slideMasters/_rels/slideMaster1.xml.rels PK o\6TT!ppt/notesMasters/notesMaster1.xml 7/23/19Click to edit Master text stylesSecond levelThird levelFourth levelFifth level‹#›PK o\s **,ppt/notesMasters/_rels/notesMaster1.xml.rels PK o\_rels/PK o\ $docProps/PK o\Kppt/PK o\ mppt/_rels/PK o\ ppt/charts/PK o\ppt/charts/_rels/PK o\ppt/embeddings/PK o\ ppt/media/PK o\Bppt/slideLayouts/PK o\qppt/slideLayouts/_rels/PK o\ppt/slideMasters/PK o\ppt/slideMasters/_rels/PK o\  ppt/slides/PK o\3ppt/slides/_rels/PK o\ bppt/theme/PK o\ppt/notesMasters/PK o\ppt/notesMasters/_rels/PK o\ppt/notesSlides/PK o\ppt/notesSlides/_rels/PK o\ }"}"P[Content_Types].xmlPK o\]] %_rels/.relsPK o\ȳ(docProps/app.xmlPK o\zZ(/docProps/core.xmlPK o\]rF F 2ppt/_rels/presentation.xml.relsPK o\Oݨ Z?ppt/theme/theme1.xmlPK o\͙Y`ppt/presentation.xmlPK o\X$oppt/presProps.xmlPK o\rpppt/tableStyles.xmlPK o\D >00Yqppt/viewProps.xmlPK o\H7t!tppt/slideLayouts/slideLayout1.xmlPK o\ђ77,wppt/slideLayouts/_rels/slideLayout1.xml.relsPK o\MeѢ))'yppt/slides/slide1.xmlPK o\3 qppt/slides/_rels/slide1.xml.relsPK o\.}ppt/notesSlides/notesSlide1.xmlPK o\:A*Jppt/notesSlides/_rels/notesSlide1.xml.relsPK o\ -2-2]ppt/slides/slide2.xmlPK o\2- ppt/slides/_rels/slide2.xml.relsPK o\ppt/notesSlides/notesSlide2.xmlPK o\xշ*ppt/notesSlides/_rels/notesSlide2.xml.relsPK o\׆׆ppt/slides/slide3.xmlPK o\W/ qppt/slides/_rels/slide3.xml.relsPK o\K |Ősppt/notesSlides/notesSlide3.xmlPK o\9 Y*zppt/notesSlides/_rels/notesSlide3.xml.relsPK o\QQ|ppt/slides/slide4.xmlPK o\` cppt/slides/_rels/slide4.xml.relsPK o\vsoppt/notesSlides/notesSlide4.xmlPK o\J *<ppt/notesSlides/_rels/notesSlide4.xml.relsPK o\|$OOOppt/slides/slide5.xmlPK o\5 ;)ppt/slides/_rels/slide5.xml.relsPK o\W8G+ppt/notesSlides/notesSlide5.xmlPK o\Qe*2ppt/notesSlides/_rels/notesSlide5.xml.relsPK o\OO'4ppt/slides/slide6.xmlPK o\ج+ ppt/slides/_rels/slide6.xml.relsPK o\z&ppt/notesSlides/notesSlide6.xmlPK o\=|*ppt/notesSlides/_rels/notesSlide6.xml.relsPK o\13QQppt/slides/slide7.xmlPK o\F ppt/slides/_rels/slide7.xml.relsPK o\)lppt/notesSlides/notesSlide7.xmlPK o\|g*ppt/notesSlides/_rels/notesSlide7.xml.relsPK o\0QQppt/slides/slide8.xmlPK o\6 >ppt/slides/_rels/slide8.xml.relsPK o\iސ@ppt/notesSlides/notesSlide8.xmlPK o\pO*Fppt/notesSlides/_rels/notesSlide8.xml.relsPK o\%l`'CRCRHppt/slides/slide9.xmlPK o\>$ ippt/slides/_rels/slide9.xml.relsPK o\quppt/notesSlides/notesSlide9.xmlPK o\1*Bppt/notesSlides/_rels/notesSlide9.xml.relsPK o\ )|R|RUppt/slides/slide10.xmlPK o\Ѳ!ppt/slides/_rels/slide10.xml.relsPK o\O ppt/notesSlides/notesSlide10.xmlPK o\T+ppt/notesSlides/_rels/notesSlide10.xml.relsPK o\>QIIppt/slides/slide11.xmlPK o\;!Nppt/slides/_rels/slide11.xml.relsPK o\s6ӑ *Pppt/notesSlides/notesSlide11.xmlPK o\O+Vppt/notesSlides/_rels/notesSlide11.xml.relsPK o\#Yppt/slides/slide12.xmlPK o\c!ppt/slides/_rels/slide12.xml.relsPK o\*)@ ppt/notesSlides/notesSlide12.xmlPK o\Fb+ppt/notesSlides/_rels/notesSlide12.xml.relsPK o\^^ppt/slides/slide13.xmlPK o\x!0Tppt/slides/_rels/slide13.xml.relsPK o\Ї >Vppt/notesSlides/notesSlide13.xmlPK o\yv+ ]ppt/notesSlides/_rels/notesSlide13.xml.relsPK o\uрII"_ppt/slides/slide14.xmlPK o\O!Eppt/slides/_rels/slide14.xml.relsPK o\0 Sppt/notesSlides/notesSlide14.xmlPK o\?ݤ+"ppt/notesSlides/_rels/notesSlide14.xml.relsPK o\8=7ppt/slides/slide15.xmlPK o\*R!xppt/slides/_rels/slide15.xml.relsPK o\Qz {ppt/notesSlides/notesSlide15.xmlPK o\$Q+Ӂppt/notesSlides/_rels/notesSlide15.xml.relsPK o\Jf--ppt/slides/slide16.xmlPK o\ !ppt/slides/_rels/slide16.xml.relsPK o\  ppt/notesSlides/notesSlide16.xmlPK o\ y+zppt/notesSlides/_rels/notesSlide16.xml.relsPK o\K !ppt/slideMasters/slideMaster1.xmlPK o\N),eppt/slideMasters/_rels/slideMaster1.xml.relsPK o\6TT!mppt/notesMasters/notesMaster1.xmlPK o\s **,ppt/notesMasters/_rels/notesMaster1.xml.relsPKcc~t