1 / 4

Link State Routing Extensions for ASON Routing

This document proposes additions to OSPFv2 and IS-IS routing protocols to support address prefixes, link attributes, and cross-layer relationships in ASON routing. It also discusses mechanisms for propagating routing information between higher and lower level RCs.

victorfrancis
Download Presentation

Link State Routing Extensions for ASON Routing

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. Link State Routing Protocols Extensions for ASON Routingdraft-dimitri-ccamp-gmpls-ason-routing-sol-00.txt IETF64 - Vancouver - Nov’05 <dpapadimitriou@psg.com>

  2. Additions Reachability Link Attributes Scoping Hierarchy OSPFv2 Extend top level Node Attribute sub-TLVs to support address IPv4/IPv6 prefixes (two new sub-TLVs) Representation of cross/inter-layer relationships as part of top-level link TLV (no encoding proposed yet for IACD sub-TLV) TE link advertisements to allow for retrieving their respective local-remote TE Router_ID relationship(s) => new sub-TLV of top level link TLV (local/remote TE Router_ID) Prefixes part of the reachability advertisements (using Node Attribute top level TLV) needs to be associated to their respective local TE Router_ID => new sub-TLV of top level Node attribute TLV (local TE Router_ID) Mechanism by which Type 10 Opaque LSA (Type 1) may carry a particular piece of routing information has been learned from a higher level RC when propagated to a lower level RC (avoid looping) - not yet specified Extensions - OSPF

  3. Additions Reachability Link Attributes Scoping Hierarchy IS-IS Not defined (see next) Representation of cross/inter-layer relationships as part of Extended IS Reachability TLV (no encoding proposed yet for IACD sub-TLV) Extended IS Reachability TLVs to allow for retrieving their respective local-remote TE Router_ID relationship(s) - not yet specified Depends on reachability encoding Extend the up/down bit mechanisms to propagate the summarized topology traffic engineering information as well as reachability information - not yet specified Extensions - IS-IS

  4. Open Issues (1) 1) OSPFv3 • Draft does not address OSPFv3 (reason: no deployment of v3 for GMPLS CP) => specific need ? • Solution: leave OSPFv3-TE extensions when needed ? 2) Reachability • Draft addresses numbered v4/v6 reachable prefixes • Need to address unnumbered IF (e.g. UNI) ? Other sub-TLV ? 3) IS-IS • Extended IP Reachability TLV (Type 135) focuses on IP reachable end-points => solution TBD

More Related