RFC 8517 on An Inventory of Transport-Centric Functions Provided by Middleboxes: An Operator Perspective

rfc-editor@rfc-editor.org Wed, 06 February 2019 00:23 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 8CF441288BD for <ietf-announce@ietfa.amsl.com>; Tue, 5 Feb 2019 16:23:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id QASyKX999fVf for <ietf-announce@ietfa.amsl.com>; Tue, 5 Feb 2019 16:23:09 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 07C1412426E for <ietf-announce@ietf.org>; Tue, 5 Feb 2019 16:23:09 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 1AD9FB82973; Tue, 5 Feb 2019 16:23:04 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg1MTcgb24gQW4gSW52ZW50b3J5IG9mIFRyYW5zcG9ydC1DZW50cmljIEZ1bmN0aW9ucyBQcm92aWRlZCBieSBNaWRkbGVib3hlczogQW4gT3BlcmF0b3IgUGVyc3BlY3RpdmU=?=
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20190206002304.1AD9FB82973@rfc-editor.org>
Date: Tue, 5 Feb 2019 16:23:04 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/bGUupyD_5QAB_47m3B5lvMSdyZg>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Feb 2019 00:23:10 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 8517

        Title:      An Inventory of Transport-Centric Functions 
                    Provided by Middleboxes: An Operator Perspective 
        Author:     D. Dolson, Ed.,
                    J. Snellman,
                    M. Boucadair, Ed.,
                    C. Jacquenet
        Status:     Informational
        Stream:     Independent
        Date:       February 2019
        Mailbox:    ddolson@acm.org, 
        Pages:      21
        Characters: 46317
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-dolson-transport-middlebox-05.txt

        URL:        https://www.rfc-editor.org/info/rfc8517

        DOI:        10.17487/RFC8517

This document summarizes an operator's perception of the benefits
that may be provided by intermediary devices that execute functions
beyond normal IP forwarding.  Such intermediary devices are often
called "middleboxes".

RFC 3234 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.

INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC