Transcript Multicast Applications

BRUW
Bandwidth
Reservation for
User
Work
Bob Riddle – Technologist
What is BRUW?
Bandwidth Reservation for User Work:
is a part of Internet2’s Hybrid Optical and Packet
Infrastructure (HOPI) project
will allow authorized users to reserve
bandwidth across packet switched backbone
networks
uses a Web-based interface for end-users to
place reservations and the MPLS protocol to set
up dedicated paths on packet switched networks,
such as Abilene
Why BRUW?
Need for bandwidth: Cal Tech - CERN
 currently email process, “personal” authentication
 Need to know every network engineer in the world
 Network equipment is manually configured
 User with need is far removed from the process
Purpose of BRUW
minimize human efforts in this process
streamline/automate this process
allow bandwidth reservations to be
made with minimal human intervention
allow end-users to send large amounts
of data reliably across packet switched
networks
simplify the reservation process for both
end-users and network managers
BRUW Design Criteria
End Users not Network Engineers … so:
“front-end” user interface must be
usable to the Researcher, Faculty, etc.
“back-end” network interface must be
trusted by the NOC
Credible bandwidth reservation requests
can be made across administrative
domains (networks )
BRUW Design Criteria (part 2)
Web Browser chosen for user interface
• users are familiar with this interface
• Web server are a “commodity” service
Separate “back-end” network
component from “front-end” user
interface
User required to authenticate and can
have different capabilities
• Shibboleth – inter-institutional middleware service
How does BRUW work?
Bandwidth Reservation
 User must register for ID
• Human intervention required
 Approved user permitted to
make a bandwidth request
 User request is either
accepted or refused
• Depends upon who you are!
• Attributes are assigned to users
 Accept request queued in
Database
How does BRUW work? (part 2)
Edge node discovery
How does BRUW work? (part 3)
every hour – checks the Scheduler DB
BRUW configures each edge router to build a bidirectional MPLS tunnel between the two end-points:
BRUW communicates with the Abilene edge routers
using JUNOScript, the communication API for Juniper
Networks routers.
BRUW connects to each edge router using
JUNOScript API, makes necessary changes to the
configuration to build and/or delete MPLS tunnels,
commits the configuration changes, and closes the
connection.
BRUW – work to be done
Policy issues – who decides?
Last mile
• MPLS tunnel across the backbone, but what about
your packet switched network?
non-packet switched networks
• CA*NET4, NLR, “new” Surfnet
• other “BRUW’s” – DRAC, UCLP, DRAGON, etc.
Non-academic networks
• ESNET collaboration at LBL
If you want to know more …
Email me – [email protected]
BRUW Notes on the Web
HOPI Project
UCLP Project
Dragon Project