%% You should probably cite rfc7436 instead of this I-D. @techreport{ietf-l2vpn-ipls-09, number = {draft-ietf-l2vpn-ipls-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-ipls/09/}, author = {François Le Faucheur and Giles Heron and Eric C. Rosen and Himanshu C. Shah}, title = {{IP-Only LAN Service (IPLS)}}, pagetotal = 30, year = ** No value found for 'doc.pub_date.year' **, month = ** No value found for 'doc.pub_date' **, day = ** No value found for 'doc.pub_date.day' **, abstract = {A Virtual Private LAN Service (VPLS) {[}VPLS{]} is used to interconnect systems across a wide-area or metropolitan-area network, making it appear that they are on a private LAN. The systems which are interconnected may themselves be LAN switches. If, however, they are IP hosts or IP routers, certain simplifications to the operation of the VPLS are possible. We call this simplified type of VPLS an "IP-only LAN Service" (IPLS). In an IPLS, as in a VPLS, LAN interfaces are run in promiscuous mode, and frames are forwarded based on their destination MAC addresses. However, the maintenance of the MAC forwarding tables is done via signaling, rather than via the MAC address learning procedures specified in {[}IEEE 802.1D{]}. This draft specifies the protocol extensions and procedures for support of the IPLS service.}, }