80 likes | 308 Views
63rd IETF - Paris. draft-wijnands-mpls-ldp-mcast-ext-00. IJsbrand Wijnands (ice@cisco.com) Bob Thomas (rhthomas@cisco.com) Yuji Kamite (y.kamite@ntt.com) Hitoshi Fukuda (hitoshi.fukuda@ntt.com). Multicast LDP. Receiver driven P2MP LSP’s Receiver driven MP2MP LSP’s
E N D
63rd IETF - Paris draft-wijnands-mpls-ldp-mcast-ext-00 IJsbrand Wijnands (ice@cisco.com) Bob Thomas (rhthomas@cisco.com) Yuji Kamite (y.kamite@ntt.com) Hitoshi Fukuda (hitoshi.fukuda@ntt.com)
Multicast LDP • Receiver driven P2MP LSP’s • Receiver driven MP2MP LSP’s • Use root address to build a path through a network. • Each intermediate hop does a route up to determine the next-hop.
Multicast LDP (cont) • Unicast routing will provide loop free P2MP and MP2MP trees. • FEC consists of: • Root address • Tree type • Opaque value
In-band signaling • Egress routers encode multicast stream information in a opaque value. • Ingress routers parse the opaque encoding and send it to Multicast. • Note, P-routers don’t need to parse the opaque value.
In-band signaling (cont) • There is a one-2-one mapping between a multicast stream and a P2MP LSP • No aggregation
Out-of-band signaling • Multicast to P2MP LSP mapping is carried via an external protocol. • MLDP opaque value carries a TID. • TID is assigned by the external protocol. • Allows for aggregation.
MP2MP LSP’s • A MP2MP LSP is build using a collection of label replication states. • There is one label state for downstream • There is a upstream label state for each downstream interface. • Upstream label states are merged with downstream states.