7/29/94 RSVP WG Slide 1 Lixia Zhang, Xerox PARC

Interface & Interaction between

RSVP and Routing

Previous talk: longer term

This talk: proposal for short term approach

? Orientation of routes

? Quality of routes

? Stability of routes & service (in absence of failure)

? Adaptation to topological changes

7/29/94 RSVP WG Slide 2 Lixia Zhang, Xerox PARC

Orientation of routes

? Requirement: receivers make reservation

? Today: routes are from souce to destination, RSVP uses path msgs to lay reverse path state

? Future: routes available from either direction

Quality of routes

? Requirement: selected paths should have sufficient resources

? Today: routes have no quality associated.

RSVP does not plan to fix this routing problem.

? Future: Request and receive quality routes

7/29/94 RSVP WG Slide 3 Lixia Zhang, Xerox PARC

Stability of routes and services

? Requirement: Service should not be disrupted in absence of failure

? Today:
Different opinions regarding the degree of route flapping;
Consensus from last meeting: do nothing for now

? Future: stable routes, smooth switchover to new routes (optional)

7/29/94 RSVP WG Slide 4 Lixia Zhang, Xerox PARC

Adaptation to topological changes

? Requirement: ASAP

? Today: RSVP uses timeout to detect failures,then (1)notify affected sources to refresh
(2)teardown the broken path fragments

? Future: Routing provides prompt failure notification, two options for repaire:
(1)intermediate routers attempt local repair, or (2)intermediate routers notify the ends to refresh