| Policy
Constrained Routing Review |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| • | Policy
Constrained Routing, Explicit Routing |
||||||||||||||
| Objectives |
|||||||||||||||
| • | Solve long
standing “fish problem” by use of single |
||||||||||||||
| router node to
create multiple policies or “routing |
|||||||||||||||
| instances” |
|||||||||||||||
| • | Use more than
destination as criteria for routing |
||||||||||||||
| decision |
|||||||||||||||
| • | At minimum use
Source (VPN membership or L3 |
||||||||||||||
| Info) +
Destination for route decision |
|||||||||||||||
| • | Technology
evolution offers solution |
||||||||||||||
| • | RFC 2547bis and
MPLS |
||||||||||||||
