RFC 7436: IP-Only LAN Service (IPLS)
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC7436
- Published
- January 2015
- Authors
- H. Shah; E. Rosen; F. Le Faucheur; G. Heron
- Status
- HISTORIC
- Stream
- IETF
- Area
- rtg
- Pages
- 32
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7438Multipoint LDP (mLDP) In-Band Signaling with WildcardsCurrent
January 2015
- RFC 7439Gap Analysis for Operating IPv6-Only MPLS NetworksCurrent
January 2015
- RFC 7432BGP MPLS-Based Ethernet VPNUpdated
February 2015
- RFC 7431Multicast-Only Fast RerouteCurrent
August 2015
- RFC 7441Encoding Multipoint LDP (mLDP) Forwarding Equivalence Classes (FECs) in the NLRI of BGP MCAST-VPN RoutesCurrent
January 2015
- RFC 7442Carrying Protocol Independent Multicast - Sparse Mode (PIM-SM) in Any-Source Multicast (ASM) Mode Trees over Multipoint LDP (mLDP)Current
February 2015
- RFC 7446Routing and Wavelength Assignment Information Model for Wavelength Switched Optical NetworksCurrent
February 2015
- RFC 7447Deprecation of BGP Entropy Label Capability AttributeCurrent
February 2015
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?