RFC 8086: GRE-in-UDP Encapsulation
In plain English — editorial summary, not part of the RFC
This document specifies a method of encapsulating network protocol packets within GRE and UDP headers. This GRE-in-UDP encapsulation allows the UDP source port field to be used as an entropy field. This may be used for load-balancing of GRE traffic in transit networks using existing Equal-Cost Multipath (ECMP) mechanisms. There are two applicability scenarios for GRE-in-UDP with different requirements: (1) general Internet and (2) a traffic-managed controlled environment. The controlled environment has less restrictive requirements than the general Internet.
Document record
- Document ID
- RFC8086
- Published
- March 2017
- Authors
- L. Yong; E. Crabbe; X. Xu; T. Herbert
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 27
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8085UDP Usage GuidelinesUpdated
March 2017
- RFC 8084Network Transport Circuit BreakersCurrent
March 2017
- RFC 8083Multimedia Congestion Control: Circuit Breakers for Unicast RTP SessionsCurrent
March 2017
- RFC 8095Services Provided by IETF Transport Protocols and Congestion Control MechanismsCurrent
March 2017
- RFC 8075Guidelines for Mapping Implementations: HTTP to the Constrained Application Protocol (CoAP)Current
February 2017
- RFC 8100Diffserv-Interconnection Classes and PracticeCurrent
March 2017
- RFC 8108Sending Multiple RTP Streams in a Single RTP SessionCurrent
March 2017
- RFC 8132PATCH and FETCH Methods for the Constrained Application Protocol (CoAP)Current
April 2017
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?