1 / 5

Requirements for OSPF Topology-Transparent Zone

Requirements for OSPF Topology-Transparent Zone. Gregory Cauchie (greg.cauchie@gmail.com ) Ning So (ning.so@tatacommunications.com ) Vic Liu (liuzhiheng@chinamobile.com) Mehmet Toy (mehmet_toy@cable.comcast.com) Lei Liu (liulei.kddi@gmail.com ) Huaimo Chen (huaimo.chen@huawei.com)

kyros
Download Presentation

Requirements for OSPF Topology-Transparent Zone

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. Requirements for OSPF Topology-Transparent Zone Gregory Cauchie (greg.cauchie@gmail.com) Ning So (ning.so@tatacommunications.com) Vic Liu (liuzhiheng@chinamobile.com) Mehmet Toy (mehmet_toy@cable.comcast.com) Lei Liu (liulei.kddi@gmail.com) Huaimo Chen (huaimo.chen@huawei.com) Renwei Li (renwei.li@huawei.com)

  2. Area in OSPF Area 1 Area 2 Area 3 Area 5 Area 4 Area 1 Area 2 Area 3 Area 4 Area 5 Area 0 Area 0 Area 0 • It provides 2 levels of hierarchies • backbone area and non backbone areas • Splitting an area into more areas for scalability, but • it is a very challenging task since significant network architecture changes • It may interrupt the services carried by the network, thus reduce the availability of the network • Hiding area topology for convergence, but • it makes end to end service set up very complex since network topology beyond an area boundary can not be seen by a node inside the area • These may lead to more work and expense on network operation and maintenance

  3. Good Parts of Both Area 0 Area 0 TTZ1 TTZ1 Area 0 TTZ2 TTZ2 TTZ3 TTZ3 TTZ4 TTZ4 • TTZ provides 1+ levels of hierarchies • TTZs in an area • Splitting parts of an area into TTZs for scalability, • It is easy since no significant network architecture changes • It is smooth, services carried by network may not be affected, availability of network is high • Hiding TTZ topology for convergence, • Network topology beyond TTZ boundary is visible to a node in TTZ and to a node in area • E2E service crossing TTZs can be easily set up • These may lead to less work and expense on network operation and maintenance

  4. Requirements for TTZ TTZ MUST be backward compatible Migration to TTZ SHOULD be smooth Migration from TTZ back to original SHOULD be smooth TTZ MUST be able to reduce the size of topology more than one order of magnitudes E2E service crossing TTZs SHOULD be set up easily Protection on service crossing TTZs SHOULD be transparent Configuration on TTZ SHOULD be minimum Changes to existing protocols for TTZ SHOULD be minimum

  5. Next Step • Welcome comments

More Related