Title: Procedures%20for%20Dynamically%20Signaled%20Hierarchical%20Label%20Switched%20Paths%20draft-ietf-ccamp-lsp-hierarchy-bis-01.txt
1Procedures for Dynamically Signaled Hierarchical
Label Switched Pathsdraft-ietf-ccamp-lsp-hierarc
hy-bis-01.txt
- Nov. 6, 2006
- Kohei Shiomoto, Richard Rabbat
- Arthi Ayyangar, Adrian Farrel, Zafar Ali
2Goal of this ID
- How to let the egress node know that an FA-LSP
needs to be advertised as an FA, or as a RA, or
only to be locally used. - Equally applicable to both numbered and
unnumbered TE links. - Identify the routing instance in which the
TE-link should be advertised.
Ingress (RTR-IDa)
Egress (RTR-IDb)
TE-link
TE-LINK-IDx
TE-LINK-IDy
TE-LINK-IDx R,F TII
LSP_TUNNEL_INTERFACE_ID Object
TE-LINK-IDy R,F TII
3Document status
- (Re)-defined LSP_TUNNEL_INTERFACE_ID Object
- R-bit
- F-bit
- Target IGP Instance ID
- To do
- Support of bundled link
4Support of bundled link
- A newly established LSP constitutes a component
link of the bundle. - The component link id has to be exchanged.
- Association between the component link and the
bundled TE-link is made.
Ingress (RTR-IDa)
Egress (RTR-IDb)
TE-LINK-IDx
TE-LINK-IDy
TE-link
COMPONENT-LINK-IDi
COMPONENT-LINK-IDj
5Next step
- Add treatment for bundled link.
- Solicit feedback from the WG.
6Backup slides
7Coding of R,F bits
R,F Behavior
0,0 neither the FA nor RA (used as a local link)
0,1 only advertised as FA
1,0 only advertised as RA
1,1 advertised as RA in both IP and MPLS-TE topologies
this table applies to bi-directional LSP only
8Target IGP Instance
IGP instance 1
IGP instance 0
Ingress (RTR-IDa)
Egress (RTR-IDb)
TE-link
TE-LINK-IDx
TE-LINK-IDy
TE-LINK-IDx R,F TII1
LSP_TUNNEL_INTERFACE_ID Object
TE-LINK-IDy R,F TII1
9Existing mechanism forNumbered TE-link
Ingress (RTR-IDa)
Egress (RTR-IDb)
TE-link
TE-LINK-IDx
Sender Template object
tunnel sender address x
TE-LINK-IDx where x /31 address of x
LSA RTR-IDa LINK-IDb
LSP_TBL
ingress egress TE-LINK-ID
Search for a
LSA RTR-IDb LINK-IDa
a b x