%% You should probably cite rfc4762 instead of this I-D. @techreport{ietf-l2vpn-vpls-ldp-09, number = {draft-ietf-l2vpn-vpls-ldp-09}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-l2vpn-vpls-ldp/09/}, author = {Marc Lasserre and Vach Kompella}, title = {{Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling}}, pagetotal = 31, year = 2006, month = jun, day = 5, abstract = {This document describes a Virtual Private LAN Service (VPLS) solution using pseudowires, a service previously implemented over other tunneling technologies and known as Transparent LAN Services (TLS). A VPLS creates an emulated LAN segment for a given set of users; i.e., it creates a Layer 2 broadcast domain that is fully capable of learning and forwarding on Ethernet MAC addresses and that is closed to a given set of users. Multiple VPLS services can be supported from a single Provider Edge (PE) node. This document describes the control plane functions of signaling pseudowire labels using Label Distribution Protocol (LDP), extending RFC 4447. It is agnostic to discovery protocols. The data plane functions of forwarding are also described, focusing in particular on the learning of MAC addresses. The encapsulation of VPLS packets is described by RFC 4448. {[}STANDARDS-TRACK{]}}, }