RFC 2890: Key and Sequence Number Extensions to GRE
In plain English — editorial summary, not part of the RFC
This document describes extensions by which two fields, Key and Sequence Number, can be optionally carried in the GRE Header. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2890
- Published
- September 2000
- Authors
- G. Dommety
- Status
- PROPOSED STANDARD
- Stream
- Legacy
- Area
- —
- Pages
- 7
- Also known as
- —
- Updates:
- RFC 2784
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3147Generic Routing Encapsulation over CLNS NetworksCurrent
July 2001
- RFC 1701Generic Routing Encapsulation (GRE)Current
October 1994
- RFC 7588A Widely Deployed Solution to the Generic Routing Encapsulation (GRE) Fragmentation ProblemCurrent
July 2015
- RFC 7676IPv6 Support for Generic Routing Encapsulation (GRE)Current
October 2015
- RFC 8313Use of Multicast across Inter-domain Peering PointsCurrent
January 2018
- RFC 8350Alternate Tunnel Encapsulation for Data Frames in Control and Provisioning of Wireless Access Points (CAPWAP)Current
April 2018
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?