RFC 4638: Accommodating a Maximum Transit Unit/Maximum Receive Unit (MTU/MRU) Greater Than 1492 in the Point-to-Point Protocol over Ethernet (PPPoE)
In plain English — editorial summary, not part of the RFC
The Point-to-Point Protocol over Ethernet (PPPoE), as described in RFC 2516, mandates a maximum negotiated Maximum Receive Unit (MRU) of 1492. This document outlines a solution that relaxes this restriction and allows a maximum negotiated MRU greater than 1492 to minimize fragmentation in next-generation broadband networks. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4638
- Published
- September 2006
- Authors
- P. Arberg; D. Kourkouzelis; M. Duckett; T. Anschutz; J. Moisand
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 9
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4636Foreign Agent Error Extension for Mobile IPv4Current
October 2006
- RFC 4640Problem Statement for bootstrapping Mobile IPv6 (MIPv6)Current
September 2006
- RFC 4635HMAC SHA (Hashed Message Authentication Code, Secure Hash Algorithm) TSIG Algorithm IdentifiersObsoleted
August 2006
- RFC 4649Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Relay Agent Remote-ID OptionCurrent
August 2006
- RFC 4620IPv6 Node Information QueriesCurrent
August 2006
- RFC 4605Internet Group Management Protocol (IGMP) / Multicast Listener Discovery (MLD)-Based Multicast Forwarding ("IGMP/MLD Proxying")Current
August 2006
- RFC 4604Using Internet Group Management Protocol Version 3 (IGMPv3) and Multicast Listener Discovery Protocol Version 2 (MLDv2) for Source-Specific MulticastCurrent
August 2006
- RFC 4592The Role of Wildcards in the Domain Name SystemCurrent
July 2006
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?