1 / 7

BAR Two Stage Service Reservation

BAR Two Stage Service Reservation. SR Stage SA Stage Linking a SA to a SR Issues. BAR SR Stage. SR Request Flow. HLM asks BAR for a SR BAR asks NSAP if a SR is possible NSAP answers yes or no. If NSAP says yes BAR asks the local and remote L-NSAP to create SR.

vanya
Download Presentation

BAR Two Stage Service Reservation

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 Two Stage Service Reservation • SR Stage • SA Stage • Linking a SA to a SR • Issues

  2. BAR SR Stage

  3. SR Request Flow • HLM asks BAR for a SR • BAR asks NSAP if a SR is possible • NSAP answers yes or no. • If NSAP says yes BAR asks the local and remote L-NSAP to create SR. • If both L-NSAP say yes then the reservation is successful. • If any L-NSAP says no then cancel NSAP SR and cancel any L-NSAP SR.

  4. BAR SA Stage

  5. SA Request Flow • HLM asks BAR for SA. • BAR asks local and remote L-NSAP if SA is possible • If both local and remote L-NSAP say “yes” then the SA is successful. • If one L-NSAP says “no” then cancel other L-NSAP SA.

  6. Linking a SA to a SR • Using a SR-ID (Explicit linking of a SA to a SR) • Provides a usability issue for clients of BAR (HLM) since “actor” for a SR is likely to be different from “actor” for SA. • Using addresses of source/destination IP subnets (Implicit linking of a SA to a SR) • No usability issue for client of BAR.

  7. Issues • It is possible last mile to be over booked. What stage should we do summing of aggregation – SR or SA ? • E.g. if SR/SA to be done between Sites. A<->B and A<->C, then a common last mile is used between SR/SA. • In SR interface, • Should we distinguish between service types? • If we do not distinguish between the service types then what values do we use for metrics like, packet loss? (for future) • If we do distinguish between service types then what do we specify in SR for GDFT. In this case SR and SA have to be the same type • What is the proper general solution?

More Related