Ticket #469 (assigned task)

Opened 3 months ago

Last modified 2 months ago

Stanford OF demo of packet and circuit convergence (OFSTAN-PCC)

Reported by: hdempsey@bbn.com Assigned to: hdempsey@bbn.com (accepted)
Priority: major Milestone:
Component: OFSTAN Version: SPIRAL2
Keywords: GEC8 Cc: sd2@stanford.edu, yiannisy@stanford.edu
Dependencies:

Description

request from Surat Das (sd2@stanford.edu) on 6/20:

"My name is Saurav Das and I am a PhD student at Stanford. I work with Prof. Guru Parulkar and Prof. Nick McKeown? in the OpenFlow project. My colleague Yiannis Yiakoumis and I would like to demo our work on packet and circuit network convergence at GEC8.

http://www.openflowswitch.org/wk/index.php/PAC.C

With that in mind, we tried to create a demo request ticket today on the GEC8 wiki. In order to create a ticket, I subscribed to the GENI working group mailing list, for the substrate working group. However, with that information I was unable to login to the wiki - I didn't get a login ID - my email id and password did not allow me to login.

Our demo requirements are simple -- we would like a couple of displays (preferably at least one big) and a wired Internet connection. Could you please let us know how we could login and create this ticket?"

Change History

06/21/10 15:11:14 changed by hdempsey@bbn.com

  • status changed from new to assigned.
  • owner changed from somebody to hdempsey@bbn.com.
  • cc set to sd2@stanford.edu, yiannisy@stanford.edu.

Provided Saurav with login information and asked him to add the completed template to this ticket.

06/21/10 16:02:37 changed by sd2@stanford.edu

1. Brief demo description (A few sentences suitable for a GEC8 attendee information page)

Packet and Circuit switched networks are typically planned, operated and managed separately, leading to substantial management overhead, functionality & resource duplication, and increased Capex & Opex. We propose and demonstrate a converged network, where OpenFlow is used to control both switching technologies in a common way, allowing the service provider maximum flexibility in using the correct mix of technologies while designing and operating their networks. Specifically, we will demonstrate how circuit flow properties (guaranteed bandwidth and delay, no jitter, bandwidth-on-demand) can be used to provide differential treatment to different types of aggregated packet flows - voice, video and web traffic.

2. List of equipment that will need AC connections (e.g. laptop, switch hardware prototype, monitor). (Just put in the number of connections needed if your demo description already lists the equipment)

Total: 6 -- > 3 PCs (2 laptops and 1 desktop), and 3 displays

3. Number of wired network connections (include required bandwidth if significant)

Two. We can bring our own Ethernet switch so we use just one wall jack - but we will still need two IP addrs.

4. Number of wireless network connections (include required bandwidth if significant)

Two

5. Projector (NO)

Monitor (YES, VGA) - we need 3 displays (ideally one big, and two small)

6. Number of posters (poster boards are 20" x 30")

One

7. Number of static addresses needed (if any)

DHCP is ok for the two wired connections.

8. Description of any special requests (e.g. VLANS to NLR or I2 backbone)

N/A

07/18/10 15:46:36 changed by hdempsey@bbn.com

  • summary changed from Stanford OF demo of packet and circuit convergence to Stanford OF demo of packet and circuit convergence (OFSTAN-PCC).