RFC 1702: Generic Routing Encapsulation over IPv4 networks
In plain English — editorial summary, not part of the RFC
This memo addresses the case of using IP as the delivery protocol or the payload protocol and the special case of IP as both the delivery and payload. This memo also describes using IP addresses and autonomous system numbers as part of a GRE source route. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC1702
- Published
- October 1994
- Authors
- S. Hanks; T. Li; D. Farinacci; P. Traina
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 4
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1701Generic Routing Encapsulation (GRE)Current
October 1994
- RFC 1692Transport Multiplexing Protocol (TMux)Current
August 1994
- RFC 1744Observations on the Management of the Internet Address SpaceCurrent
December 1994
- RFC 2041Mobile Network TracingCurrent
October 1996
- RFC 1335A Two-Tier Address Structure for the Internet: A Solution to the Problem of Address Space ExhaustionCurrent
May 1992
- RFC 2098Toshiba's Router Architecture Extensions for ATM : OverviewCurrent
February 1997
- RFC 2286Test Cases for HMAC-RIPEMD160 and HMAC-RIPEMD128Current
February 1998
- RFC 2367PF_KEY Key Management API, Version 2Current
July 1998
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?