Beneficial Functions of Middleboxes
draft-dolson-transport-middlebox-00

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Last updated 2017-12-03 (latest revision 2017-06-01)
Replaces draft-dolson-plus-middlebox-benefits
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
IETF conflict review conflict-review-dolson-transport-middlebox
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-dolson-transport-middlebox-00.txt

Abstract

This document summarizes benefits that operators perceive to be provided by intermediary devices that provide functions apart from normal IP forwarding. Such intermediary devices are often called "middleboxes". RFC3234 defines a taxonomy of middleboxes and issues in the Internet. Most of those middleboxes utilize or modify application-layer data. This document primarily focuses on devices that observe and act on information carried in the transport layer, and especially information carried in TCP packets. A primary goal of this document is to provide information to working groups developing new transport protocols, to aid understanding of what might be gained or lost by design decisions that may affect (or be affected by) middlebox operation.

Authors

David Dolson (ddolson@sandvine.com)
Juho Snellman (jsnellman@sandvine.com)
Mohamed Boucadair (mohamed.boucadair@orange.com)
Christian Jacquenet (christian.jacquenet@orange.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)