IP-Only LAN Service (IPLS) (RFC7436)
Original Publication Date: 2015-Jan-01
Included in the Prior Art Database: 2015-Jan-15
Internet Society Requests For Comment (RFCs)
H. Shah: AUTHOR [+4]
This document defines a Historic Document for the Internet community. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741.
Internet Engineering Task Force (IETF) H. Shah Request for Comments: 7436 Cinea Corp. Category: Historic E. Rosen ISSN: 2070-1721 Juniper Networks F. Le Faucheur G. Heron Cisco Systems January 2015
IP-Only LAN Service (IPLS)
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 that 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 Media Access Control (MAC) addresses. However, the maintenance of the MAC forwarding tables is done via signaling, rather than via the MAC address learning procedures specified in the IEEE's "Media Access Control (MAC) Bridges". This document 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 Provider Edge (PE) routers that were not capable of learning MAC addresses through data plane. This became a non-issue with newer hardware. The concepts put forth by this document 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 it is published simply as a historic record of the ideas.
Shah, et al. Historic [Page 1]
RFC 7436 IPLS January 2015
Status of This Memo
This document is not an Internet Standards Track specification; it is published for the historical record.
This document def...