RFC 4562: MAC-Forced Forwarding: A Method for Subscriber Separation on an Ethernet Access Network
In plain English — editorial summary, not part of the RFC
This document describes a mechanism to ensure layer-2 separation of Local Area Network (LAN) stations accessing an IPv4 gateway over a bridged Ethernet segment. The mechanism - called "MAC-Forced Forwarding" - implements an Address Resolution Protocol (ARP) proxy function that prohibits Ethernet Media Access Control (MAC) address resolution between hosts located within the same IPv4 subnet but at different customer premises, and in effect directs all upstream traffic to an IPv4 gateway. The IPv4 gateway provides IP-layer connectivity between these same hosts. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4562
- Published
- June 2006
- Authors
- T. Melsen; S. Blake
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 13
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4332Cisco's Mobile IPv4 Host Configuration ExtensionsCurrent
December 2005
- RFC 5171Cisco Systems UniDirectional Link Detection (UDLD) ProtocolCurrent
April 2008
- RFC 7586The Scalable Address Resolution Protocol (SARP) for Large Data CentersCurrent
June 2015
- RFC 8743Multiple Access Management Services Multi-Access Management Services (MAMS)Current
March 2020
- RFC 4391Transmission of IP over InfiniBand (IPoIB)Updated
April 2006
- RFC 5007DHCPv6 LeasequeryCurrent
September 2007
- RFC 5071Dynamic Host Configuration Protocol Options Used by PXELINUXCurrent
December 2007
- RFC 3925Vendor-Identifying Vendor Options for Dynamic Host Configuration Protocol version 4 (DHCPv4)Current
October 2004
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?