1. ECE 544 Group Project : Routing
KC Huang

2. Objective
Application: message multicast. A message is sent from one sender to 1~3 recipients.
Design a protocol used for this application.
Implement the protocol
Inter-operation Test

3. Application Message Delivery Each message contains header and payload
The header contains multiple recipient addresses (names). a b
a,b,c
hello c

4. Network Elements End Nodes (User): Routers Links
Has 1 port linking to a router
No direct link between end nodes.
Routers
Connect to other routers or end-nodes
Has 2~4 ports.
Links
not reliable.
lose packets with probability p in both directions

5. Requirement 1: Address User Address Open Issues:
All end nodes share a same naming scheme
Open Issues:
Routers name and address
Fix or dynamic address assignment
Routers address is assigned or fix?
End nodes address is assigned or fix?

6. Requirement 2: Routing
The routing protocol can route traffic among any end nodes.
No static routing
The same routing protocol must run on every router.
Open Issues:
Discovery
Periodic hello message or Hello with ACK
Routing protocol/algorithm
DV/Distributed Bellman-Ford : RIP packet
LV/Dijkstra : LSP packet
Multicast Routing algorithm

7. Requirement 3: Reliability
Message delivery must be guaranteed.
Design Issue:
ARQ
Hop-by-hop ARQ?
End-to-End ARQ?
Stop-and-wait or sliding windows?

8. Project Plan Standards & Documents
Draft slide (4%) is due before 1st Std. Meeting (3/26 5pm)
Each team’s standard document (4%) (4/2)
Final Submission & Demo
Standard
Meeting
2nd Std.
Meeting
start
end
Final Design Document (4/6)
3-4 people to form a group
May be held on (3/30)
Standards & Documents
Coding, Integration/Test, Demo preparation

9. What is in Protocol Draft?
How to fulfill the requirements?
Issues:
Address
Packet Formats
Node and Router discovery
Message delivery
Routing/Forwarding schemes
Interface between Routers (link will die?)
Interface between End-Node and Router ……

10. Standard Meeting
Each group gives a minutes talk about the design
Submit the draft slide to me before 3/26 5pm
Other groups can challenge…
Discuss
What shall be in the standard? what shall not?
What’s the best way to do a certain task?
Vote if not reach a consensus
Select members for a protocol-writing team.
2nd Meeting to settle down final details.
Distribute the final document to all groups

11. Software Design Issues
Recommend to reuse your current design of ports, links, addresses…
Shall support duplex communication
Not constrained by the current architecture. (common.cpp common.h)

12. Demo
The student group uses one or more connected computers running Linux to show the demo.
The demo network shall contain AT LEAST 4 end- nodes and AT LEAST 3 routers.
 Network Start
Start each router program in different console on one or more computers. Make necessary configurations (should not configure routing table manually).
If there is some routing/discovery signaling exchanged, indicate the procedure of building routing table on the console output.

13. Demo Cntd. Start application to verify the message delivery
Start end-nodes with different IDs. Configure the end-nodes (make each of them link to a router). Let them discovered by router.
When you think routers are ready for supporting end-to-end traffic, the user types the text message and desired receiver ID(s) in a console of one end-node. Then commands to send it.
In the consoles of router which route this message, the router shall ‘display’ the reception of this message and what action it takes to forward this message.
In the console of receiver, the messages reception must be shown.

14. Final Submission Router program ( Source code + Makefile)
Sender and receiver program to test (Source code + Makefile)
Guide: How to run your program
Document for Protocol implementation and Performance Evaluation. It could contain, but not limited to, following topics:
Signaling definition
Routing/Discovery procedure
Interfaces of router-router and router-terminal (end-node)
Performance estimation/evaluation

15. Have Fun!