1 / 7

BAR Interface

BAR Interface. Matching SR and SA Services GDFT VLL GDFT SR will accept a File Size (data volume). A user should specify TimeForAverage (not enforced) so that accurate bandwidth can be requested from the backbone GDFT SA will also accept File Size and Time Window.

eithne
Download Presentation

BAR Interface

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. BAR Interface • Matching SR and SA Services • GDFT • VLL • GDFT SR will accept a File Size (data volume). • A user should specify TimeForAverage (not enforced) so that accurate bandwidth can be requested from the backbone • GDFT SA will also accept File Size and Time Window. • cross check whether GDFT SA bandwidth <= GDFT SR bandwidth • VLL SR will accept forward and, optional, reverse bandwidth over a time window. • VLL SA will also accept same input. • cross check whether VLL SA bandwidth <= VLL SR bandwidth To change: View -> Header and Footer

  2. BAR Interface • Operations (as they’d appear in a WSDL): • CreateGDFTReservation • CreateVLLReservation • QueryReservation • CancelReservation • ActivateGDFT • ActivateVLL • QueryActivation • CancelActivation • Do not want to group SR and SA operations into port types in the WSDL as this would generate two different services. • In future, names of SA operations may change if/when SR stage disappears. To change: View -> Header and Footer

  3. Reservation Request • We think the GDFT Reservation request should contain: • FileSize (mandatory) • StartTime (mandatory) • EndTime (mandatory) • Source (mandatory) • Destination (mandatory) • TimeForAverage (optional) • Calculation of bandwidth • If TimeForAverage is provided, • Bandwidth = SafetyFactor * (FileSize/TimeForAverage) • If not, • Bandwidth = SafetyFactor*(FileSize/(EndTime –StartTime)) • Note, use the same formula to calculate the bandwidth for GDFT Service Activations. To change: View -> Header and Footer

  4. Reservation Request • VLL Reservation request should contain: • ForwardBandwidth (mandatory) • ReverseBandwidth (optional) • StartTime (mandatory) • EndTime (mandatory) • Source (mandatory) • Destination (mandatory) • Note, “TimeForAverage” is not used here. • Safety factor is not used as the reservation is to be made for the exact bandwidth that user wants. To change: View -> Header and Footer

  5. Reservation Request (cont.) • Source/Destination • Valid values are: • IPv4 Addresses • IPv6 Addresses • Subnet Addresses • Shall we include • Port? – to allow a more fine-granular reservation • Yes, as an optional parameter at SR • Shall we allow • Multiple subnets (as supported by NSAP)? • Yes To change: View -> Header and Footer

  6. Reservation Response • SR response contains: • SR-ID • Status • A user would have to use the “QueryReservation” operation to check whether the SR is confirmed by NSAP. • Necessary as NSAP uses the asynchronous communication model. • How does BAR knows Reservation is successful or not ? BAR could either , • pull status from NSAP (make requests to NSAP until a condition is satisfied. • Or NSAP could push status to BAR (notification) To change: View -> Header and Footer

  7. Service Activation • Requires addition of optional parameter “SR-ID” to requests. • Synchronous communication as only L-NSAPs are involved. • Again, shall we add “port” at source/destination? To change: View -> Header and Footer

More Related