Generic Routing Encapsulation (GRE)

Farinacci, Dino; Li, T.; Hanks, S.; Meyer, David; Traina, P.

doi:10.17487/rfc2784

Cited by 339 publications

(150 citation statements)

References 0 publications

Supporting

Mentioning

146

Contrasting

Unclassified

Order By: Relevance

“…For example, typically, multiplexing of data units from a host happens at the network layer, and stateful connections and congestion control happen at the transport layer. Recently many of these functions are being repeated at many layers in the stack, where stateful connections can occur at the link (circuit), network (tunnel, e.g., for GRE [20], MPLS [47], or even to provide enhancements, e.g., using PEPs [9]), transport (connection), and even higher layers (in multiplexing layers such as BEEP [46]). …”

Section: Related Workmentioning

confidence: 99%

A Dynamic Recursive Unified Internet Design (DRUID)

Touch¹,

Baldin

Dutta

et al. 2011

Computer Networks

View full text Add to dashboard Cite

a b s t r a c tThe Dynamic Recursive Unified Internet Design (DRUID) is a future Internet design that unifies overlay networks with conventional layered network architectures. DRUID is based on the fundamental concept of recursion, enabling a simple and direct network architecture that unifies the data, control, management, and security aspects of the current Internet, leading to a more trustworthy network. DRUID's architecture is based on a single recursive block that can adapt to support a variety of communication functions, including parameterized mechanisms for hard/soft state, flow and congestion control, sequence control, fragmentation and reassembly, compression, encryption, and error recovery. This recursion is guided by the structure of a graph of translation tables that help compartmentalize the scope of various functions and identifier spaces, while relating these spaces for resource discovery, resolution, and routing. The graph also organizes persistent state that coordinates behavior between individual data events (e.g., coordinating packets as a connection), among different associations (e.g., between connections), as well as helping optimize the recursive discovery process through caching, and supporting prefetching and distributed pre-coordination. This paper describes the DRUID architecture composed of these three parts (recursive block, translation tables, persistent state), and highlights its goals and benefits, including unifying the data, control, management, and security planes currently considered orthogonal aspects of network architecture.

show abstract

Section: Related Workmentioning

confidence: 99%

A Dynamic Recursive Unified Internet Design (DRUID)

Touch¹,

Baldin

Dutta

et al. 2011

Computer Networks

View full text Add to dashboard Cite

show abstract

“…Headers which can be part of extension header chains include a) the AH header b) the null ESP header c) the minimal encapsulation header [RFC2004, section 3.1] d) the GRE header [GRE1,GRE2] e) IPv6 extension headers.…”

Section: List Compressionmentioning

confidence: 99%

RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed

Degermark¹

2001

341

312

View full text Add to dashboard Cite

This document specifies a highly robust and efficient header compression scheme for RTP/UDP/IP (Real-Time Transport Protocol, User Datagram Protocol, Internet Protocol), UDP/IP, and ESP/IP (Encapsulating Security Payload) headers.Existing header compression schemes do not work well when used over links with significant error rates and long round-trip times. For many bandwidth limited links where header compression is essential, such characteristics are common.

show abstract

“…Minimal Encapsulation and GRE encapsulation is done in an analogous manner, following RFC 2004 [5] for Minimal Encapsulation and RFC 2784 [8] for GRE Encapsulation, but using outer IP, UDP and MIP headers in place of the outer IP header.…”

Section: Encapsulating Ip Headers In Udpmentioning

confidence: 99%

“…GRE encapsulated traffic is processed according to RFC 2784 [8] and RFC 1701 [3], with the delivery header consisting of the outer IP, UDP and MIP headers.…”

Section: Decapsulationmentioning

confidence: 99%