1. 73rd IETF - Minneapolis I. Wijnandsice@cisco.com T. Eckerteckert@cisco.com N. Leymannnicolai.leymann@t-systems.com M. Napieralamnapierala@att.com draft-wijnands-mpls-mldp-in-band-signaling-00

2. mLDP in-band signaling draft-wijnands-mpls-in-band-signaling-00 Should have been published as: draft-wijnands-mpls-mldp-in-band-signaling-00

3. Problem we’re solving Come up with a simple way to transport global table multicast traffic across a MPLS core. No need for additional signaling. No need for L3VPN procedures. Dynamic mapping of multicast streams to LSPs.

4. Solution Multicast tree information, like (S,G) or (*/M,G) is encoded in the opaque field of the mLDP FEC by the egress router(s). The mLDP LSP is build through the MPLS core. The root of the P2MP LSP or leaf of the MP2MP LSP parses the opaque field and passes it to the multicast component. Multicast component deals with the information as if it had received a PIM join.

5. Solution (cont) Works for multicast flows where the tree information is known by the egress router. This is typically for SSM, Bidir and sparse-mode sources. Each IP multicast flow creates a unique LSP in the core.

6. Opaque encodings We defined 4 new opaque encodings: Transit IPv4 Source TLV Transit IPv6 Source TLV Transit IPv4 bidir TLV Transit IPv6 bidir TLV

7. Transit IPv4 Source TLV 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | Source +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Group +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Type: 2 (to be assigned by IANA). Length: 8 Source: IPv4 multicast source address, 4 octets. Group: IPv4 multicast group address, 4 octets.

8. Transit IPv6 Source TLV 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | Source ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ~ | Group ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ~ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Type: 3 (to be assigned by IANA). Length: 32 Source: IPv6 multicast source address, 16 octets. Group: IPv6 multicast group address, 16 octets.

9. Transit IPv4 bidir TLV 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | Mask Len | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Group | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Type: 4 (to be assigned by IANA). Length: 5 Mask Len: The number of contiguous one bits that are left justified and used as a mask, 1 octet. Group: IPv4 multicast group address, 4 octets.

10. Transit IPv6 bidir TLV 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | Mask Len | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Group ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ~ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Type: 5 (to be assigned by IANA). Length: 17 Mask Len: The number of contiguous one bits that are left justified and used as a mask, 1 octet. Group: IPv6 multicast group address, 16 octets.

11. Scalability Each IP multicast flow maps to a LSP. Works well if the number of multicast flows is under control by the operator. mLDP is receiver driven, so its expected to scale well for thousands of LSPs.

12. Going forward Authors like to get comments on the draft.

13. Questions?