The MPLS WG Archive[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index] LDP support for deaggregation as described in MPLS Arch MPLS an d Hop by Hop Routed Traffic
Jim, -> > 1. This example implies to me that an LSR must be able to -> support the -> > ability to be both an egress and an ingress for the same FEC, in -> > this case 10.2/16. For example R2 must be the deaggregation -> > point and thus the egress for 10.2/16, which will force a BMP -> > lookup which may then match 10.2/16(because it didn't match -> > either of the more specific routes), causing a labeled packet -> > to be sent to R3. -> > Is my understanding of this correct ? -> -> Yes. R2 must terminate the incoming LSP, do an IP lookup and -> forward the packet in a new LSP. Addition to what Shahram said, this is "a kind of" LSP stitching. As the LDP and RSVP-TE standards stands, LDP can establish a single LSP (with out stitched) from one routing to another domain (for example, different ISIS levels or OSPF areas). But when it comes to aggregation (here in the above example) if R2 is an L1/2 or ABR router then the LSR is internally split into egress LER and ingress LER to stitch the LSP across routing domains. It is a normal convention, at least people think, that the LSP stitching is applicable only in TE environments only using RSVP-TE (again, because, RSVP-TE as it stands now can't do TE across different TE domains) Cheers. -- Venkata |
|