Skip to main content

A Widely Deployed Solution to the Generic Routing Encapsulation (GRE) Fragmentation Problem
draft-ietf-intarea-gre-mtu-05

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: RFC Editor <rfc-editor@rfc-editor.org>
Subject: Document Action: 'A Widely-Deployed Solution To The Generic Routing Encapsulation (GRE) Fragmentation Problem' to Informational RFC (draft-ietf-intarea-gre-mtu-05.txt)

The IESG has approved the following document:
- 'A Widely-Deployed Solution To The Generic Routing Encapsulation (GRE)
   Fragmentation Problem'
  (draft-ietf-intarea-gre-mtu-05.txt) as Informational RFC

This document is the product of the Internet Area Working Group.

The IESG contact persons are Brian Haberman and Terry Manderson.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-intarea-gre-mtu/


Ballot Text

Technical Summary

GRE [RFC2784] is a protocol that allows the encapsulation of an arbitrary network layer protocol over another arbitrary network layer protocol. The GRE protocol specification does not define how to handle fragmentation, and this has led to several implementation specific ways of doing this. A GRE tunnel will operate correctly only if its ingress and egress nodes support compatible fragmentation solutions. This document describes a widely deployed GRE fragmentation solution used by multiple vendors.

Working Group Summary

The individual draft that led to this working group draft was initially aimed at becoming a BCP. There was some controversy in the working group as to whether the solution documented in the draft was the best way of doing things. This led to the document being re-oriented as Informational with the explicit goal of documenting existing deployments.

Document Quality

Yes. There are multiple interoperable implementations of the solution described in this draft. Two major router vendors already support the specification. The solution is also widely deployed and is in use on the Internet.

Personnel

Suresh Krishnan is the document shepherd. Brian Haberman is the responsible AD.

RFC Editor Note