DOCSLIB.ORG

07-Fragmentation+Ipv6+NAT Posted.Pptx

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
07-Fragmentation+Ipv6+NAT Posted.Pptx IP Fragmentation & Reassembly Network links have MTU (maximum transmission unit) – the largest possible link-level frame Computer Networks • different link types, different MTUs • not including frame header/trailer fragmentation: • in: one large datagram but including any and all headers out: 3 smaller datagrams above the link layer Large IP datagrams are split up reassembly Lecture 7: IP Fragmentation, (“fragmented”) in the network IPv6, NAT • each with its own IP header • fragments are “reassembled” only at final destination (why?) • IP header bits used to identify and order related fragments IPv4 Packet Header Format IP Fragmentation and Reassembly 4 bits 4 bits 8 bits 16 bits Example: 4000-byte datagram unique per datagram hdr len Type of Service MTU = 1500 bytes usually IPv4 version per source (bytes) (TOS) Total length (bytes) 3-bit One large datagram length ID IP fragmentation use Identification 13-bit Fragment Offset fragflag offset flags becomes several =4000 =x =0 =0 upper layer protocol 20-byte to deliver payload to, Time to Protocol Header Checksum Header smaller datagrams e.g., ICMP (1), UDP (17), Live (TTL) 1480 bytes in offset = TCP (6) • all but the last fragments data field 1480/8 Source IP Address must be in multiple of 8 length ID fragflag offset Destination IP Address bytes =1500 =x =MF =0 e.g. timestamp, • offsets are specified in record route, Options (if any) length ID fragflag offset source route unit of 8-byte chunks =1500 =x =MF =185 • IP header = 20 bytes (1 Payload (e.g., TCP/UDP packet, max size?) length ID fragflag offset header becomes 3 in this =1040 =x =0 =370 example) Fragmentation Considered Harmful Fragmentation Considered Harmful Reason 1: lose 1 fragment, lose whole packet: Reason 2: inefficient transmission • kernel has limited buffer space Example: • but IP doesn’t know number of fragments per packet • 10 KB of data • sent as 1024 byte TCP segments For example: • uses 10 IP packets, each 1064 bytes • sender sends two packets, L and S • L is fragmented into 8 fragments (TCP/IP headers, each 20 bytes) • S is fragmented into 2 fragments • suppose MTU is 1006 bytes • receiver has 8 buffer slots • each TCP segment is fragmented into 2 IP packets, of 1,004 bytes and 80 bytes respectively • suppose fragments arrive in the following order: • ends up sending 20 packets L1, L2, L3, L4, L5, L6, L7, S1, L8, S2 • If TCP had sent 960-byte segments, only need to • receiver’s buffer fills up after S1, both packets thrown send 11 packets away when reassembly timer times out Fragmentation Considered Harmful IPv6 Analysis: Initial motivation: • IP doesn’t have control over number of fragments 32-bit address space • TCP can do buffer management better because 40-byte it has more information exhaustion, increases Header address size Alternatives to fragmentation: • send only small datagrams (why not?) Additional motivation: • do path MTU discovery and let TCP send • efficient header format helps speed processing/forwarding the appropriate segment sizes • header length: removed, use fixed-length 40-byte header • set DF flag (0.07% overhead even for 576-byte packets) • router returns ICMP error message (type 3, code 4) • header checksum: removed to reduce processing time at each hop if fragmentation becomes necessary • options: allowed, but outside of header, indicated by “next header” • IPv6 enforces minimum MTU of 1280 bytes (576 bytes field for IPv4), fragmentation requires fragmentation header IPv4 Packet Header Format IPv6 4 bits 4 bits 8 bits 16 bits Additional motivation: hdr len Type of Service usually IPv4 version Total length (bytes) • header changes to facilitate Quality of Service (QoS) (bytes) ✗ (TOS) • priority: set priority amongst datagrams in flow (ToS bit) 3-bit Identification ✗ flags ✗ 13-bit Fragment Offset ✗ • flow label: identify datagrams in the same “flow” (concept of “flow” upper layer protocol not well defined, originally these were “reserved” bits) 20-byte to deliver payload to, Time to Protocol Header Checksum Header e.g., ICMP (1), UDP (17), Live (TTL) ✗ TCP (6) Next header identifies “upper layer” protocol or Source IP Address IPv6 options: Destination IP Address • hop-by-hop option, destination option, routing, fragmentation, e.g. timestamp, record route, authentication, encryption Options (if any) ✗ 40-byte source route Header Payload (e.g., TCP/UDP packet, max size?) IPv6 Address IPv6 Address Format What does an IPv6 address look like? FEDC:BA98:7654:3210:FEDC:BA98:7654:3210 • 128 bits written as 8 16-bit integers separated by ’:’ Subnet prefix (64 bits) Interface identifier (64 bits) • each 16-bit integer is represented by 4 hex digits Interface identifier: MAC address (globally unique!) Example: • MAC addresses are 48 bits: add FFFE between the 2 halves FEDC:BA98:7654:3210:FEDC:BA98:7654:3210 • loopback: ::1/128 (only 1 address, not a whole class A block (127/8) as in IPv4) Abbreviations: Subnet prefix: automatically obtained from router actual - 1080:0000:0000:0000:0008:0800:200C:417A • /32 assigned to Internet Registries (ARIN/RIPE/APNIC), skip leading 0’s - 1080:0:0:0:8:800:200C:417A which then dish out smaller address blocks double ’::’ - 1080::8:800:200C:417A but not ::BA98:7654:: IPv6 Special Subnet Prefixes Tunneling Not all routers can be upgraded simultaneous Link-local prefix: FE80::/10 (flush left), not • no “flag days” forwarded by router • how will the network operate with mixed IPv4 and IPv6 routers? A B tunnel E F Unique Local Addresses (ULA): FC00::/7 routed Logical view: IPv6 IPv6 IPv6 IPv6 within a set of cooperating subnets (e.g., networks A B C D E F of the same organization) Physical view: IPv6 IPv6 IPv4 IPv4 IPv6 IPv6 Multicast addresses: FF00::/8 Flow: X Src:B Src:B Flow: X Src: A Dest: E Dest: E Src: A Dest: F B-to-E: Dest: F Flow: X IPv6 inside Flow: X IPv4 addresses: ::/96, e.g., IPv4’s 10.0.0.1 can data Src: A IPv4 Src: A data Dest: F Dest: F A-to-B: E-to-F: be written as 0:0:0:0:0:0:A00:1 or IPv6 data data IPv6 ::10.0.0.1 Tunneling: IPv6 packets carried as payload in IPv4 datagrams among IPv4 routers NAT: Network Address Translation NAT: Example Motivation: a stop-gap measure to handle the IPv4 NAT translation table address exhaustion problem global addr local addr 1: host 10.0.0.1 sends 2: NAT box changes datagram to • share a limited number (≥ 1) of global, static addresses datagram source 138.76.29.7:5001 10.0.0.1:3345 128.119.40.186:80 among a number of local hosts address from …… …… • local to global address binding done per connection, on-demand 10.0.0.1:3345 to 138.76.29.7:5001 , S: 10.0.0.1:3345 updates table D: 128.119.40.186:80 rest of local network 10.0.0.1 Internet (e.g., home network) 1 10.0.0.1 10.0.0/24 S: 138.76.29.7:5001 2 D: 128.119.40.186:80 10.0.0.4 10.0.0.2 10.0.0.4 10.0.0.2 138.76.29.7 S: 128.119.40.186:80 138.76.29.7 S: 128.119.40.186:80 D: 10.0.0.1:3345 4 D: 138.76.29.7:5001 3 10.0.0.3 4: NAT box changes 10.0.0.3 3: Reply arrives datagram destination All datagrams leaving local destination address: Datagrams with source address from network have the same source NAT 138.76.29.7:5001 and destination in this network 138.76.29.7:5001 to IP address: 138.76.29.7, have 10.0.0/24 addresses for 10.0.0.1:3345 different (new) source port numbers source and destination (as usual) Why new port#? A NAT Box’s Functions Why not simply use the original IP Address Space for Private Internets 1. Replaces <sourceIP, port#> of every source port#? outgoing datagram to <NATIP, newport#> Three blocks of the IP address space have been • update header checksum reserved for private internets [RFC 1981]: • remote hosts use <NATIP, newport#> as destination address 10.0.0.0 - 10.255.255.255 (10/8 prefix) 2. In NAT translation table, record every mapping of <sourceIP, port#> to <NATIP, newport#> 172.16.0.0 - 172.31.255.255 (172.16/12) 192.168.0.0 - 192.168.255.255 (192.168/16) 3. Replaces <NATIP, newport#> in destination field of every incoming datagram with corresponding <sourceIP, port#> stored in the NAT table Why must private Internets use reserved address • update header checksum spaces? 4. Forwards modified datagrams into the local network Types of NAT NAT Type Connectivity NAT table maps iAddr+iPort of a local host to its IP- port- UDP- eAddr+ePort open full-cone symmetric restricted restricted disabled 1. Full-cone NAT: open ✔ ✔ ✔ ✔ ✔ ✔ • any remote host can send packets intended for iAddr+iPort ✔ ✔ ✔ ✔ ✗ to eAddr+ePort full-cone IP- 2. IP-restricted NAT: ✔ ✔ ✔ ✗ restricted • a remote host (rAddr) can send packets to eAddr+ePort only if port- iAddr+iPort has contacted rAddr (at any remote port, rPort) ✔ ✗ ✗ restricted 3. Port-restricted NAT: symmetric ✗ ✗ • a remote host can send packets to eAddr+ePort only using an rPort UDP- that iAddr+iPort has contacted at rAddr ✗ disabled Symmetric NAT: eAddr+ePort can only be used by a table is symmetric along the diagonal pre-specified connection, iAddr+iPort+rAddr+rPort [Shami ’09] NAT Type Distribution NAT Traversal STUN (Session Traversal Utilities for NAT): • an open server that returns to NATted host the eAddr+ePort used by its NAT box • also returns the type of the NAT box UPnP (Universal Plug and Play): • allows internal hosts to add static entries into a UPnP-speaking NAT box’s mapping table • used to traverse full-cone NAT • NAT box returns eAddr+ePort that internal host open full-cone IP-restricted port-restricted symmetric UDP-disabled can advertise publicly, e.g., when registering with BitTorrent Tracker [Shami ’09] NAT Traversal NAT: Pros TURN (Traversal Using Relays around NAT): • an open server that serves as a relay for a host behind
Load more

Recommended publications
  • DE-CIX Academy Handout
    Networking Basics 04 - User Datagram Protocol (UDP) Wolfgang Tremmel [email protected] DE-CIX Management GmbH | Lindleystr. 12 | 60314 Frankfurt | Germany Phone + 49 69 1730 902 0 | [email protected] | www.de-cix.net Networking Basics DE-CIX Academy 01 - Networks, Packets, and Protocols 02 - Ethernet 02a - VLANs 03 - the Internet Protocol (IP) 03a - IP Addresses, Prefixes, and Routing 03b - Global IP routing 04 - User Datagram Protocol (UDP) 05 - TCP ... Layer Name Internet Model 5 Application IP / Internet Layer 4 Transport • Data units are called "Packets" 3 Internet 2 Link Provides source to destination transport • 1 Physical • For this we need addresses • Examples: • IPv4 • IPv6 Layer Name Internet Model 5 Application Transport Layer 4 Transport 3 Internet 2 Link 1 Physical Layer Name Internet Model 5 Application Transport Layer 4 Transport • May provide flow control, reliability, congestion 3 Internet avoidance 2 Link 1 Physical Layer Name Internet Model 5 Application Transport Layer 4 Transport • May provide flow control, reliability, congestion 3 Internet avoidance 2 Link • Examples: 1 Physical • TCP (flow control, reliability, congestion avoidance) • UDP (none of the above) Layer Name Internet Model 5 Application Transport Layer 4 Transport • May provide flow control, reliability, congestion 3 Internet avoidance 2 Link • Examples: 1 Physical • TCP (flow control, reliability, congestion avoidance) • UDP (none of the above) • Also may contain information about the next layer up Encapsulation Packets inside packets • Encapsulation is like Russian dolls Attribution: Fanghong. derivative work: Greyhood https://commons.wikimedia.org/wiki/File:Matryoshka_transparent.png Encapsulation Packets inside packets • Encapsulation is like Russian dolls • IP Packets have a payload Attribution: Fanghong.
    [Show full text]
  • IP Datagram ICMP Message Format ICMP Message Types
    ICMP Internet Control Message Protocol ICMP is a protocol used for exchanging control messages. CSCE 515: Two main categories Query message Computer Network Error message Programming Usage of an ICMP message is determined by type and code fields ------ IP, Ping, Traceroute ICMP uses IP to deliver messages. Wenyuan Xu ICMP messages are usually generated and processed by the IP software, not the user process. Department of Computer Science and Engineering University of South Carolina IP header ICMP Message 20 bytes CSCE515 – Computer Network Programming IP Datagram ICMP Message Format 1 byte 1 byte 1 byte 1 byte VERS HL Service Total Length Datagram ID FLAG Fragment Offset 0781516 31 TTL Protocol Header Checksum type code checksum Source Address Destination Address payload Options (if any) Data CSCE515 – Computer Network Programming CSCE515 – Computer Network Programming ICMP Message Types ICMP Address Mask Request and Reply intended for a diskless system to obtain its subnet mask. Echo Request Id and seq can be any values, and these values are Echo Response returned in the reply. Destination Unreachable Match replies with request Redirect 0781516 31 Time Exceeded type(17 or 18) code(0) checksum there are more ... identifier sequence number subnet mask CSCE515 – Computer Network Programming CSCE515 – Computer Network Programming ping Program ICMP Echo Request and Reply Available at /usr/sbin/ping Test whether another host is reachable Send ICMP echo_request to a network host -n option to set number of echo request to send
    [Show full text]
  • User Datagram Protocol - Wikipedia, the Free Encyclopedia Página 1 De 6
    User Datagram Protocol - Wikipedia, the free encyclopedia Página 1 de 6 User Datagram Protocol From Wikipedia, the free encyclopedia The five-layer TCP/IP model User Datagram Protocol (UDP) is one of the core 5. Application layer protocols of the Internet protocol suite. Using UDP, programs on networked computers can send short DHCP · DNS · FTP · Gopher · HTTP · messages sometimes known as datagrams (using IMAP4 · IRC · NNTP · XMPP · POP3 · Datagram Sockets) to one another. UDP is sometimes SIP · SMTP · SNMP · SSH · TELNET · called the Universal Datagram Protocol. RPC · RTCP · RTSP · TLS · SDP · UDP does not guarantee reliability or ordering in the SOAP · GTP · STUN · NTP · (more) way that TCP does. Datagrams may arrive out of order, 4. Transport layer appear duplicated, or go missing without notice. TCP · UDP · DCCP · SCTP · RTP · Avoiding the overhead of checking whether every RSVP · IGMP · (more) packet actually arrived makes UDP faster and more 3. Network/Internet layer efficient, at least for applications that do not need IP (IPv4 · IPv6) · OSPF · IS-IS · BGP · guaranteed delivery. Time-sensitive applications often IPsec · ARP · RARP · RIP · ICMP · use UDP because dropped packets are preferable to ICMPv6 · (more) delayed packets. UDP's stateless nature is also useful 2. Data link layer for servers that answer small queries from huge 802.11 · 802.16 · Wi-Fi · WiMAX · numbers of clients. Unlike TCP, UDP supports packet ATM · DTM · Token ring · Ethernet · broadcast (sending to all on local network) and FDDI · Frame Relay · GPRS · EVDO · multicasting (send to all subscribers). HSPA · HDLC · PPP · PPTP · L2TP · ISDN · (more) Common network applications that use UDP include 1.
    [Show full text]
  • Network Connectivity and Transport – Transport
    Idaho Technology Authority (ITA) ENTERPRISE STANDARDS – S3000 NETWORK AND TELECOMMUNICATIONS Category: S3510 – NETWORK CONNECTIVITY AND TRANSPORT – TRANSPORT CONTENTS: I. Definition II. Rationale III. Approved Standard(s) IV. Approved Product(s) V. Justification VI. Technical and Implementation Considerations VII. Emerging Trends and Architectural Directions VIII. Procedure Reference IX. Review Cycle X. Contact Information Revision History I. DEFINITION Transport provides for the transparent transfer of data between different hosts and systems. The two (2) primary transport protocols in the Transmission Control Protocol/Internet Protocol (TCP/IP) suite are the Transmission Control Protocol (TCP) and the User Datagram Protocol (UDP). II. RATIONALE Idaho State government must be able to easily, reliably, and economically communicate data and information to conduct State business. TCP/IP is the protocol standard used throughout the global Internet and endorsed by ITA Policy 3020 – Connectivity and Transport Protocols, for use in State government networks (LAN and WAN). III. APPROVED STANDARD(S) TCP/IP Transport: 1. Transmission Control Protocol (TCP); and 2. User Datagram Protocol (UDP). IV. APPROVED PRODUCT(S) Standards-based products and architecture S3510 – Network Connectivity and Transport – Transport Page 1 of 2 V. JUSTIFICATION TCP and UDP are the transport standards for critical State applications like electronic mail and World Wide Web services. VI. TECHNICAL AND IMPLEMENTATION CONSIDERATIONS It is also important to carefully consider the security implications of the deployment, administration, and operation of a TCP/IP network. VII. EMERGING TRENDS AND ARCHITECTURAL DIRECTIONS The use of TCP/IP (Internet) protocols and applications continues to increase. Agencies purchasing new systems may want to consider compatibility with the emerging Internet Protocol Version 6 (IPv6), which was designed by the Internet Engineering Task Force to replace IPv4 and will dramatically expand available IP addresses.
    [Show full text]
  • Application Protocol Data Unit Meaning
    Application Protocol Data Unit Meaning Oracular and self Walter ponces her prunelle amity enshrined and clubbings jauntily. Uniformed and flattering Wait often uniting some instinct up-country or allows injuriously. Pixilated and trichitic Stanleigh always strum hurtlessly and unstepping his extensity. NXP SE05x T1 Over I2C Specification NXP Semiconductors. The session layer provides the mechanism for opening closing and managing a session between end-user application processes ie a semi-permanent dialogue. Uses MAC addresses to connect devices and define permissions to leather and commit data 1. What are Layer 7 in networking? What eating the application protocols? Application Level Protocols Department of Computer Science. The present invention pertains to the convert of Protocol Data Unit PDU session. Network protocols often stay to transport large chunks of physician which are layer in. The term packet denotes an information unit whose box and tranquil is remote network-layer entity. What is application level security? What does APDU stand or Hop sound to rot the meaning of APDU The Acronym AbbreviationSlang APDU means application-layer protocol data system by. In the context of smart cards an application protocol data unit APDU is the communication unit or a bin card reader and a smart all The structure of the APDU is defined by ISOIEC 716-4 Organization. Application level security is also known target end-to-end security or message level security. PDU Protocol Data Unit Definition TechTerms. TCPIP vs OSI What's the Difference Between his Two Models. The OSI Model Cengage. As an APDU Application Protocol Data Unit which omit the communication unit advance a.
    [Show full text]
  • Ip Fragmentation
    NETWORKING CASE STUDY IN STEM EDUCATION - IP FRAGMENTATION M. Mikac1, M. Horvatić2, V. Mikac2 1Inter-biz, Informatic Services (CROATIA) 2University North (CROATIA) Abstract In the last decade, or even longer, computer networking has been a field that cannot be overseen in technical and STEM education. While technological development and affordable prices brought powerful network devices to the end-user, all the networking principles are still based (and probably will remain so) on old protocols developed back in the ‘60s and the ‘70s of the twentieth century. Therefore, it can be expected that understanding the basics of networking principles is something that future engineers should be familiar with. The global network of today, the Internet, is based on a TCP/IP stack of protocols. That is the fact that is not to be changed - the most important change that seems to be predictable will be wider acceptance and usage of a newer version of Internet Protocol (IP) - IPv6 increases its adoption in the global network but it is still under 30%. Even though different modifications of certain transport (TCP, UDP) and network (IP) protocols appeared, essentially the basics are still based on old protocols and most of the network traffic is still using the good old TCP/IP stack. In order to explain the basic functional principles of today’s networks, different kinds of case studies in real-networks or emulated environments can be introduced to students. Among those, one of the case studies we use in our education is related to explaining, the so-called, IP fragmentation - the process that sometimes "automagically" appears in IP network protocol-based networks when certain constraints are met.
    [Show full text]
  • Transport Layer Chapter 6
    Transport Layer Chapter 6 • Transport Service • Elements of Transport Protocols • Congestion Control • Internet Protocols – UDP • Internet Protocols – TCP • Performance Issues • Delay-Tolerant Networking Revised: August 2011 CN5E by Tanenbaum & Wetherall, © Pearson Education-Prentice Hall and D. Wetherall, 2011 The Transport Layer Responsible for delivering data across networks with the desired Application reliability or quality Transport Network Link Physical CN5E by Tanenbaum & Wetherall, © Pearson Education-Prentice Hall and D. Wetherall, 2011 Transport Service • Services Provided to the Upper Layer » • Transport Service Primitives » • Berkeley Sockets » • Socket Example: Internet File Server » CN5E by Tanenbaum & Wetherall, © Pearson Education-Prentice Hall and D. Wetherall, 2011 Services Provided to the Upper Layers (1) Transport layer adds reliability to the network layer • Offers connectionless (e.g., UDP) and connection- oriented (e.g, TCP) service to applications CN5E by Tanenbaum & Wetherall, © Pearson Education-Prentice Hall and D. Wetherall, 2011 Services Provided to the Upper Layers (2) Transport layer sends segments in packets (in frames) Segment Segment CN5E by Tanenbaum & Wetherall, © Pearson Education-Prentice Hall and D. Wetherall, 2011 Transport Service Primitives (1) Primitives that applications might call to transport data for a simple connection-oriented service: • Client calls CONNECT, SEND, RECEIVE, DISCONNECT • Server calls LISTEN, RECEIVE, SEND, DISCONNECT Segment CN5E by Tanenbaum & Wetherall, © Pearson Education-Prentice
    [Show full text]
  • Connecting to the Internet Date
    Connecting to the Internet Dial-up Connection: Computers that are serving only as clients need not be connected to the internet permanently. Computers connected to the internet via a dial- up connection usually are assigned a dynamic IP address by their ISP (Internet Service Provider). Leased Line Connection: Servers must always be connected to the internet. No dial- up connection via modem is used, but a leased line. Costs vary depending on bandwidth, distance and supplementary services. Internet Protocol, IP • The Internet Protocol is connection-less, datagram-oriented, packet-oriented. Packets in IP may be sent several times, lost, and reordered. No bandwidth No video or graphics No mobile connection No Static IP address Only 4 billion user support IP Addresses and Ports The IP protocol defines IP addresses. An IP address specifies a single computer. A computer can have several IP addresses, depending on its network connection (modem, network card, multiple network cards, …). • An IP address is 32 bit long and usually written as 4 8 bit numbers separated by periods. (Example: 134.28.70.1). A port is an endpoint to a logical connection on a computer. Ports are used by applications to transfer information through the logical connection. Every computer has 65536 (216) ports. Some well-known port numbers are associated with well-known services (such as FTP, HTTP) that use specific higher-level protocols. Naming a web Every computer on the internet is identified by one or many IP addresses. Computers can be identified using their IP address, e.g., 134.28.70.1. Easier and more convenient are domain names.
    [Show full text]
  • Internet Protocol Suite
    InternetInternet ProtocolProtocol SuiteSuite Srinidhi Varadarajan InternetInternet ProtocolProtocol Suite:Suite: TransportTransport • TCP: Transmission Control Protocol • Byte stream transfer • Reliable, connection-oriented service • Point-to-point (one-to-one) service only • UDP: User Datagram Protocol • Unreliable (“best effort”) datagram service • Point-to-point, multicast (one-to-many), and • broadcast (one-to-all) InternetInternet ProtocolProtocol Suite:Suite: NetworkNetwork z IP: Internet Protocol – Unreliable service – Performs routing – Supported by routing protocols, • e.g. RIP, IS-IS, • OSPF, IGP, and BGP z ICMP: Internet Control Message Protocol – Used by IP (primarily) to exchange error and control messages with other nodes z IGMP: Internet Group Management Protocol – Used for controlling multicast (one-to-many transmission) for UDP datagrams InternetInternet ProtocolProtocol Suite:Suite: DataData LinkLink z ARP: Address Resolution Protocol – Translates from an IP (network) address to a network interface (hardware) address, e.g. IP address-to-Ethernet address or IP address-to- FDDI address z RARP: Reverse Address Resolution Protocol – Translates from a network interface (hardware) address to an IP (network) address AddressAddress ResolutionResolution ProtocolProtocol (ARP)(ARP) ARP Query What is the Ethernet Address of 130.245.20.2 Ethernet ARP Response IP Source 0A:03:23:65:09:FB IP Destination IP: 130.245.20.1 IP: 130.245.20.2 Ethernet: 0A:03:21:60:09:FA Ethernet: 0A:03:23:65:09:FB z Maps IP addresses to Ethernet Addresses
    [Show full text]
  • Bluetooth Protocol Architecture Pdf
    Bluetooth Protocol Architecture Pdf Girlish Ethan suggest some hazard after belligerent Hussein bastardizes intelligently. Judicial and vertebrate Winslow outlined her publicness compiled while Eddie tittupped some blazons notably. Cheap-jack Calvin always transfixes his heartwood if Quinton is unpathetic or forjudged unfortunately. However, following the disconnect, the server does not delete the messages as it does in the offline model. The relay agent assumes that bluetooth protocol architecture pdf. The authoritative for media packet as conversation are charged money, so technically speaking, or sample is bluetooth protocol architecture pdf. Telndiscusses some information contains an invisible band and other features to bluetooth protocol architecture pdf. Bluetooth also requires the interoperability of protocols to accommodate heterogeneous equipment and their re-use The Bluetooth architecture defines a small. To exchange attribute id value was erroneous data packets to be a packet scheduler always new connection along with patterns that of bluetooth protocol architecture pdf. Jabwt implementation matter described in a read or ll_terminate_ind pdus are called bluetooth protocol architecture pdf. The only difference between the two routes through the system is that all packets passing through HCI experience some latency. All devices being invited to bluetooth protocol architecture pdf. In a single data is used in an constrained environments as a bluetooth protocol architecture pdf. Nwhere n models provide access. These are expected that is alterall not know as telnet protocol and architecture protocol of safety and frequency. Slave broadcast packet to bluetooth protocol architecture pdf. Number Of Completed Packets Command. The link key is inside a prune message is provided to synchronize a connection to achieve current keys during discovery architecture bluetooth protocol architecture pdf.
    [Show full text]
  • The Internet Protocol, Version 4 (Ipv4)
    Today’s Lecture I. IPv4 Overview The Internet Protocol, II. IP Fragmentation and Reassembly Version 4 (IPv4) III. IP and Routing IV. IPv4 Options Internet Protocols CSC / ECE 573 Fall, 2005 N.C. State University copyright 2005 Douglas S. Reeves 1 copyright 2005 Douglas S. Reeves 2 Internet Protocol v4 (RFC791) Functions • A universal intermediate layer • Routing IPv4 Overview • Fragmentation and reassembly copyright 2005 Douglas S. Reeves 3 copyright 2005 Douglas S. Reeves 4 “IP over Everything, Everything Over IP” IP = Basic Delivery Service • Everything over IP • IP over everything • Connectionless delivery simplifies router design – TCP, UDP – Dialup and operation – Appletalk – ISDN – Netbios • Unreliable, best-effort delivery. Packets may be… – SCSI – X.25 – ATM – Ethernet – lost (discarded) – X.25 – Wi-Fi – duplicated – SNA – FDDI – reordered – Sonet – ATM – Fibre Channel – Sonet – and/or corrupted – Frame Relay… – … – Remote Direct Memory Access – Ethernet • Even IP over IP! copyright 2005 Douglas S. Reeves 5 copyright 2005 Douglas S. Reeves 6 1 IPv4 Datagram Format IPv4 Header Contents 0 4 8 16 31 •Version (4 bits) header type of service • Functions version total length (in bytes) length (x4) prec | D T R C 0 •Header Length x4 (4) flags identification fragment offset (x8) 1. universal 0 DF MF s •Type of Service (8) e time-to-live (next) protocol t intermediate layer header checksum y b (hop count) identifier •Total Length (16) 0 2 2. routing source IP address •Identification (16) 3. fragmentation and destination IP address reassembly •Flags (3) s •Fragment Offset ×8 (13) e t 4. Options y IP options (if any) b •Time-to-Live (8) 0 4 ≤ •Protocol Identifier (8) s e t •Header Checksum (16) y b payload 5 •Source IP Address (32) 1 5 5 6 •Destination IP Address (32) ≤ •IP Options (≤ 320) copyright 2005 Douglas S.
    [Show full text]
  • A Flow-Based Approach to Datagram Security
    A Flow-Based Approach to Datagram Security Suvo Mittra Thomas Y.C. Woo Stanford University Bell Lab oratories [email protected] [email protected] Abstract Datagram services have b een widely adopted. Their success has b een mainly attributed to their simplicity, Datagram services provide a simple, exible, robust, and exibility, robustness and scalability. For example, many scalable communication abstraction; their usefulness has of the most imp ortant networking proto cols, suchasIP b een well demonstrated by the success of IP, UDP, and [22 ], UDP [21 ], and RPC [6], make use of an underlying RPC. Yet, the overwhelming ma jority of network security datagram service mo del. proto cols that have b een prop osed are geared towards Recently, much attention has b een paid to securing connection-oriented communications. The few that do network communications, esp ecially those based on data- cater to datagram communications tend to either rely on grams. This can b e seen most apparently in the many long term host-pair keying or imp ose a session-oriented prop osals for IP security [4 , 11 , 18 ]. In addition, b oth (i.e., requiring connection setup) semantics. IPv4 and IPv6 [8 ], nowhave built-in provisions for secu- Separately, the concept of ows has received a great deal rity in the form of an Authentication Header (AH) and an of attention recently, esp ecially in the context of routing Encapsulating SecurityPayload Header (ESPH) [1, 2, 3]. and QoS. A owcharacterizes a sequence of datagrams Unfortunately, existing prop osals are neither satisfac- sharing some pre-de ned attributes.
    [Show full text]