RFC 7588: A Widely Deployed Solution to the Generic Routing Encapsulation (GRE) Fragmentation Problem
In plain English — editorial summary, not part of the RFC
This memo describes how many vendors have solved the Generic Routing Encapsulation (GRE) fragmentation problem. The solution described herein is configurable. It is widely deployed on the Internet in its default configuration.
Document record
- Document ID
- RFC7588
- Published
- July 2015
- Authors
- R. Bonica; C. Pignataro; J. Touch
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 12
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7676IPv6 Support for Generic Routing Encapsulation (GRE)Current
October 2015
- RFC 6946Processing of IPv6 "Atomic" FragmentsCurrent
May 2013
- RFC 8724SCHC: Generic Framework for Static Context Header Compression and FragmentationUpdated
April 2020
- RFC 8824Static Context Header Compression (SCHC) for the Constrained Application Protocol (CoAP)Current
June 2021
- RFC 8900IP Fragmentation Considered FragileCurrent
September 2020
- RFC 9011Static Context Header Compression and Fragmentation (SCHC) over LoRaWANCurrent
April 2021
- RFC 9363A YANG Data Model for Static Context Header Compression (SCHC)Updated
March 2023
- RFC 9391Static Context Header Compression over Narrowband Internet of ThingsCurrent
April 2023
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?