Changes between Initial Version and Version 1 of Ticket #1432
- Timestamp:
- 02/27/15 16:19:37 (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #1432
- Property Reporter changed from hdempsey@bbn.com to nxsvks@rit.edu
-
Ticket #1432 – Description
initial v1 1 One-sentence layman's description: 2 Example: This demo shows a working prototype of an emergency communication service in St. Louis, Missouri. 1 One-sentence layman's description: a demonstration to speed up emergency communications by passing the normal IP forwarding and dependency on IP routing tables. The demonstration will be conducted over Emulab testbed. Comparison with normal information forwarding using BGP will be conducted. 3 2 4 Who should see this demo? 5 Example: Attendees interested in emergency preparedness and resilient networks should see this demo. 3 Who should see this demo? Attendees interested in emergency preparedness and resilient networks should see this demo. Network professionals interested in seeing MPLS as a protocol that can be used for routing should see this demo. 6 4 7 Demo description paragraph(s): 8 “Elevator speech” description that identifies (a) what you are demonstrating and (b) why it is important. This description may be used for advance publicity and to help attendees identify the demonstrations they wish to see. 5 Demo description paragraph(s): The demonstration will be in three steps. The first one will demo the performance comparison between a tiered routing protocol and BGP. The second stage will involve adapting MPLS as a transition platform to implement routing that will bypass IP and its routing protocols and proof of concept of the same. The third stage will demonstrate a modified MPLS code running on LINUX OS that is able to route using special labels. This modified MPLS will not depend on IP and its routing protocols. 9 6 10 List of equipment that will need AC connections (e.g. laptop, switch, monitor): 11 2 12 Just put in the number of connections needed if your demo description already lists equipment. 7 List of equipment that will need AC connections (e.g. laptop, switch, monitor): 4 laptops will need AC connections + 3 monitors with AC connections 13 8 14 Total number of wired network connections (sum standard IP and VLAN connections) .9 Total number of wired network connections (sum standard IP and VLAN connections):1 standard IP wired. BW estimate 50-100 Mbps. If this is for Internet connection, we will need 4. 15 10 16 1 standard IP wired. BW estimate 50-100 Mbps.11 Number of wired layer 2 VLANs (if any): Specify VLAN number, if known, approximate bandwidth, and whether tagged or untagged. 17 12 18 Number of wired layer 2 VLANs (if any): 19 Specify VLAN number, if known, approximate bandwidth, and whether tagged or untagged. 13 Number of wireless network connections (include required bandwidth if significant): 4 20 14 21 Number of wireless network connections (include required bandwidth if significant):15 Number of static addresses needed (if any): 4 22 16 23 Number of static addresses needed (if any):17 Monitor (y/n, specify VGA or DVI): 2 VGA, 1 HDMI 24 18 25 Monitor (y/n, specify VGA or DVI): 26 1 27 Specify resolution only if your software has resolution restrictions. 19 Number of posters (max size poster boards are 30" x 40"): 2 28 20 29 Number of posters (max size poster boards are 30" x 40"): 30 1 21 Special requests: Include any specific network connectivity needs (e.g. VLANs to a particular GENI location, projects you'd like to be near, etc.) 31 22 32 Special requests:33 Include any specific network connectivity needs34 (e.g. VLANs to a particular GENI location, projects you'd like to be near, etc.)35 23 36 Estimated demo requirements submitted for PI Nirmala Shenoy from RIT based on input from USIgnite. 24 25 PI Nirmala Shenoy from RIT