File: session.README

package info (click to toggle)
nam 1.15-11
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 29,532 kB
  • sloc: cpp: 17,346; tcl: 10,655; sh: 2,997; ansic: 1,253; makefile: 139; perl: 66
file content (45 lines) | stat: -rw-r--r-- 1,196 bytes parent folder | download | duplicates (10)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
Trace file: 
	session.nam.gz

Purpose:
	demonstrate the difference in between regular (detailed) packet 
	forwarding and session level packet scheduling

Topology: 
	255 nodes and 266 links partial MBone topology 
	equal link bandwidth (512bps) and delay (10ms)
	obtained by Mark Handley's(mjh@east.isi.edu) MBone trace tools

Source:
	node 209
	noted in red

Members:
	30 of them 
	randomly selected
	noted in black

Traffic:
	1 pkt every 37.5ms
	210 bytes per packet
	starting at simulation time 1.0


Graph on the left:
	- regular/detailed multicast packet forwarding
	- packets traverse through nodes and links (basically a multicast
	tree) to reach group members.

Graph on the right:
	- session level packet scheduling
	- the delay to transfer a packet from the source to its 
	receiver is computed and a receive(pkt) event is directly 
	scheduled to happen after the delay at the receiver
	- number of red dots attached to group receivers represents the
	number of packets that have been sent and waiting to be received.
	- the larger the (delay x bandwidth) in between the source and 
	receiver, the higher the queue of red dots.


Polly Huang, Mon Mar 16 15:52:40 PST 1998
huang@isi.edu