%% You should probably cite rfc7436 instead of this I-D.
@techreport{ietf-l2vpn-ipls-15,
    number =    {draft-ietf-l2vpn-ipls-15},
    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/15/},
    author =    {Himanshu C. Shah and Eric C. Rosen and François Le Faucheur and Giles Heron},
    title =     {{IP-Only LAN Service (IPLS)}},
    pagetotal = 31,
    year =      2014,
    month =     oct,
    day =       15,
    abstract =  {A Virtual Private LAN Service (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. The original intent was to provide an alternate solution to VPLS for those PE routers that were not capable of learning MAC address through data plane. This became a non-issue with newer hardware. The concepts put forth by this draft are still valuable and are adopted in one form or other by newer work such as Ethernet VPN in L2VPN Working Group and possible data center applications. At this point, no further action is planned to update this document and is published simply as a historic record of the ideas.},
}