Anup Mathur Anusha Sheelavant Prakhar Srivastava

Slides:



Advertisements
Similar presentations
Network Layer IPv6 Slides were original prepared by Dr. Tatsuya Suda.
Advertisements

Project3 Malabika Das Prajna Setty Preeti Rao. Assumptions and Address Scheme Assumptions End hosts can only connect to one router and knows which router.
Nov 11, 2004CS573: Network Protocols and Standards1 IP Routing: OSPF Network Protocols and Standards Autumn
CSCE 515: Computer Network Programming Chin-Tser Huang University of South Carolina.
Oct 21, 2004CS573: Network Protocols and Standards1 IP: Addressing, ARP, Routing Network Protocols and Standards Autumn
CS335 Networking & Network Administration Tuesday, May 11, 2010.
IPv6 Mobility David Bush. Correspondent Node Operation DEF: Correspondent node is any node that is trying to communicate with a mobile node. This node.
CS335 Networking & Network Administration Tuesday, April 20, 2010.
Internet Command Message Protocol (ICMP) CS-431 Dick Steflik.
Gursharan Singh Tatla Transport Layer 16-May
© Janice Regan, CMPT 128, CMPT 371 Data Communications and Networking Ethernet, ARP.
ECE 544 Project 3 Content Based Routing Neelakantan Nurani Krishnan Shikha Kakkar Suja Srinivasan.
CN2668 Routers and Switches Kemtis Kunanuraksapong MSIS with Distinction MCTS, MCDST, MCP, A+
TCP/IP Protocol Suite 1 Chapter 14 Upon completion you will be able to: Unicast Routing Protocols: RIP, OSPF, and BGP Distinguish between intra and interdomain.
ECE 544 Project3 Kush Patel Siddharth Paradkar Ke Dong.
© Janice Regan, CMPT 128, CMPT 371 Data Communications and Networking BGP, Flooding, Multicast routing.
ECE 544 Project3 Team member. Assumptions and Address Scheme Assumptions End hosts can only connect to routers Same content available at multiple end.
CMPT 471 Networking II Address Resolution IPv4 ARP RARP 1© Janice Regan, 2012.
Fall 2005Computer Networks20-1 Chapter 20. Network Layer Protocols: ARP, IPv4, ICMPv4, IPv6, and ICMPv ARP 20.2 IP 20.3 ICMP 20.4 IPv6.
1 The Internet and Networked Multimedia. 2 Layering  Internet protocols are designed to work in layers, with each layer building on the facilities provided.
Hyung-Min Lee ©Networking Lab., 2001 Chapter 8 ARP and RARP.
S305 – Network Infrastructure Chapter 5 Network and Transport Layers.
1 Internet Control Message Protocol (ICMP) Used to send error and control messages. It is a necessary part of the TCP/IP suite. It is above the IP module.
ECE 544 Project3 Amith V.S Pavan Kulkarni Suneet Dixit.
Chapter 7 ARP and RARP.
Chapter 9 Hardware Addressing and Frame Type Identification 1.Delivering and sending packets 2.Hardware addressing: specifying a destination 3. Broadcasting.
Content Routing Protocol Design Karthikeyan Ganesan Shruti Venkatesh Rafay Zamir.
OV Copyright © 2013 Logical Operations, Inc. All rights reserved. TCP/IP Addressing and Data Delivery  The TCP/IP Protocol Suite  IP Addressing.
ECE 544 Project3 Group 9 Brien Range Sidhika Varshney Sanhitha Rao Puskuru.
Ad Hoc On-Demand Distance Vector Routing (AODV) ietf
ECE 544 Project3 Ali Rostami Mohsen Ghassemi Mahmoud Ramezani-Mayiami.
S305 – Network Infrastructure Chapter 5 Network and Transport Layers.
TCP/IP1 Address Resolution Protocol Internet uses IP address to recognize a computer. But IP address needs to be translated to physical address (NIC).
Address Resolution Protocol Yasir Jan 20 th March 2008 Future Internet.
ECE 544 Protocol Design Project 2016 Chengyao Wen Hua Deng Xiaoyu Duan.
ECE 544 Protocol Design Project 2016 Nirali Shah Thara Philipson Nithin Raju Chandy.
ECE 544 Protocol Design Project 2016 Michael Sherman Murtadha Aldeer Leonard T. Park.
ECE 544 Project3 Parishad Karimi Mehrnaz Tavan Sai Teja Lingam.
ECE 544 Protocol Design Project 2016 Kiran Jatty Lasya Nandamuri Varun Vinnakota.
Behrouz A. Forouzan TCP/IP Protocol Suite, 3rd Ed.
Chapter 5 Network and Transport Layers
IP: Addressing, ARP, Routing
Scaling the Network: The Internet Protocol
OSPF (Open Shortest Path First)
Objective: ARP.
ECE 544 Protocol Design Project 2016
Link-State Routing Protocols
Chapter 5 Network and Transport Layers
Net 323: NETWORK Protocols
Net 431 D: ADVANCED COMPUTER NETWORKS
ECE 544 Protocol Design Project 2016
ECE 544 Project3 Team member.
ECE 544 Protocol Design Project 2016
Mobile and Wireless Networking
ECE 544 Protocol Design Project 2016
ECE 544 Protocol Design Project 2016
Vidur Nayyar Xueting Wang Weicong Zhao
Link-State Routing Protocols
ECE 544 Project3 Team member: BIAO LI, BO QU, XIAO ZHANG 1 1.
Aayush Patidar Ashwin Ramakrishnan Manoj Juneja
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network, Enhanced Chapter 4: Planning and Configuring Routing and Switching.
Chapter 7 ARP and RARP Prof. Choong Seon HONG.
Viet Nguyen Jianqing Liu Yaqin Tang
Christopher Beyer Hajar Mahdavi-Doost Tony Thayil
Routing Fundamentals and Subnets
Link-State Routing Protocols
Scaling the Network: The Internet Protocol
ECE 544 Project3 Team member.
Ch 17 - Binding Protocol Addresses
ECE 544 Project3 Dheeraj Medikonda Ravi Chandra Godavarthi 1.
Presentation transcript:

Anup Mathur Anusha Sheelavant Prakhar Srivastava ECE 544 Project3 Anup Mathur Anusha Sheelavant Prakhar Srivastava

Assumptions Assumptions End hosts can only connect to routers Same content available at multiple end nodes All routers have static IP addresses Routing tables are updated periodically and on events Routers are allowed to send ACK’s for reliable transmission Router can connect to a maximum 5 other routers and 254 hosts.

Address Scheme Naming scheme and eventual address scheme . Router- R1,R2 .. R255 -- A.B.Rid.255 End hosts- H1, H2 .. H255 -- A.B.Rid.Hid Content- Filename Algorithm .

File name algorithm Hashing with variable data  Break the input into a sequence of small units (bits, byte, words, etc.) and combine all the units b[1], b[2], …, b[m] sequentially, as follows S ← S0; // Initialize the state. for k in 1, 2, ..., m do // Scan the input data units. S ← F(S, b[k]); // Combine data unit k into the state. return G(S, n) // Extract the hash value from the state. If b[k] are single bits, then F(S,b) could be if highbit(S) = 0 then return 2 * S + b else return (2 * S + b) ^ P Here highbit(S) - the most significant bit of S; the '*' operator denotes unsigned integer multiplication with lost overflow. '^' is the bitwise exclusive OR operation applied to words; and P is a suitable fixed word.

Content name Content id: Type: format ex: jpg,txt,mpeg Hash table value The content name : type-hashvalue

Bootstrapping and Discovery Algorithm Routers and end hosts boot up (Hello packet?) Discovery Routers discover other routers Hosts discover their router Packet Format

Bootstrapping Starting from router 0, connect router 1 Handshake packets are sent – informing the other router about the presence. Handshake packet contains the mac address and router id. If no router id is maintained, then the router with lower mac address becomes the network start router. Assigning id :0(start) to itself and the next number in the series of 5.

Bootstrapping- Contd. If the router is already connected to a network, it will allocate the next router its number based on the formula = id*5 +[1-5]. If the router already has an id, no new id is allocated. The routing table is built by using OSPF algorithm. The Algorithm also conveys the content id. If the router id is more than 255, then we use the 2nd octet of the Ip address. If two networks are to be connected, the mac address defines the subnet and is assigned in the first octet of the ip address. Each router then stores the mac address it was given and assigns itself the number given by the parent router.

Host id learning Whenever a host connects to a router, the router assigns the ip address to the host as A.B.Rid.Hid As a consequence each router can be connected to only 255 hosts as the id 255 cannot be given. The router maintains a table of the number of hosts connected, its sequentially assigned and the router maintains an alive table, which is refreshed with a timer overflow.

Hello Packet Identifier: HEL My Router ID (2 bytes) Device ID (1 byte) Guest Router ID (2 bytes) MAC Address (6 bytes) Identifier: HEL: Indicates that it is a “Hello” packet. ASN : assigning value ACK : Acknowledgement My Router ID: The ID of the sender. Guest Router ID: The ID of the router which is being assigned the ID. Device ID: ID which indicates whether the device is a router or a end Host. MAC Address: MAC Address of the sender.

Baseline Algorithm Content routing algorithm Updating the content library Searching content Content Host selection Data transfer

Updating the content library Host broadcasts the packet with : Content id Update Identifier Broadcast Address #of hops At each router we forward to all nodes other than the source. At each router we keep a copy of packet. At each router we check if the number of hops is greater than the stored packet, discard. If the router already has a copy with greater number of hops replace the copy and forward. No acknowledgements are sent by the other host upon receiving the update- hosts update their content library.

Searching Content Host broadcasts the packet with Content id Search Identifier Broadcast Address #ofhops At each router we forward to all nodes other than the source. At each router we keep a copy of packet. At each router we check if the number of hops is greater than the stored packet, discard. If the router already has a copy with greater number of hops replace the copy and forward. The content provider sends an acknowledgement back to the source.

Content Host selection At each router the packet with the lesser number of hops or smaller time is forwarded. This removes the problem of cyclic transmission in broadcasting and also helps in selection of the acknowledgement. The first acknowledgement received by the host is the path/source is chosen. If two packets come at the same time, the acknowledgment with lower number of hops is considered.

Data transfer Once the host receives an acknowledgement, a transfer packet is sent to the host selected. The transfer packet should contain the destination address where the content was found. Once the transfer packet is received, the content host starts making packets of the content and starts transmitting to the Receiving host. In transit between the routers using Sliding window(selective repeat) algorithm with a window size of 4 packets and packet id of 3 bits

Data transfer End of file: identifier tag is filled with EOF after the last data packet is sent, this closes the data transmission.

Data Transfer restrictions No of hops> 255 discard. Time to live for the copy is the N*x times the time stamp difference, for simplicity we are using the N=2. In sliding window, if the acknowledgment is not received for length of sliding window time, an event for updating the routing table is made. The time to live should be updated in the Selective sliding window if the acknowledgment is not received.

Data Transfer and Reliability Message Forward Multicast is not supported Unicast: we need the destination address Broadcast is supported for 255.255.255.255 ARQ Scheme Hop-by-hop – Sliding Window Sliding window uses selective request scheme

Source Address (4 bytes) Packet Format Identifier (4bytes) Packet id (1 byte) Content id (16 bytes) Dest Address (4 bytes) Source Address (4 bytes) Next hop (4 bytes) No of Hops (2 bytes) CRC (16 bytes) Timer (8 bytes) Time Stamp DATA Identifiers can be SEA (Search) UPD (Update) ACK (Acknowledgement) REQ (Request) DAT (Data) EOF (End of file)

Acknowledgement packet Identifier: ACK Packet id (1 byte) Content id (16 bytes) Dest Address (4 bytes) Source Address (4 bytes) Next hop (4 bytes) No of Hops (2 bytes) CRC (16 bytes) Timer (8 bytes)

Source Address (4 bytes) EOF packet Identifier: EOF Packet id (1 byte) Content id (16 bytes) Dest Address (4 bytes) Source Address (4 bytes) Next hop (4 bytes) No of Hops (2 bytes) CRC (16 bytes) Timer (8 bytes)

Advantages and Disadvantages Scalable to other networks using the first octet of the IP address to define other networks if no gateway Latency – we have tried to maintain a fast hoh-hop link state, thus using a sliding window ARQ. Disadvantage: Does not support multicast

Appendix: Network Architecture Refer to the following example scenarios for analysis purposes: Scenario 1: @host_H2: get (content_C3) H2 C1 C2 R5 C3 H1 R1 R2 R3 R4 H3

Appendix: Network Architecture Scenario 2: @host_H1: get (content_C2) H1 H2 H3 C1 C2 C3 R1 R2 R3 R4 R5

Appendix: Network Architecture Scenario 3: @host_H1: get (content_C1) H1 H2 H3 H4 C1 C1 C2 C3 C1