[ippm] RFC 9506 on Explicit Host-to-Network Flow Measurements Techniques

rfc-editor@rfc-editor.org Tue, 31 October 2023 22:37 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 426C1C151083; Tue, 31 Oct 2023 15:37:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.533
X-Spam-Level:
X-Spam-Status: No, score=0.533 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_NONE=0.793, SPF_HELO_SOFTFAIL=0.732, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r2RnBjxmlPYa; Tue, 31 Oct 2023 15:37:36 -0700 (PDT)
Received: from rfcpa.amsl.com (unknown [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE40BC1522C4; Tue, 31 Oct 2023 15:37:18 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id DE54785414; Tue, 31 Oct 2023 15:37:18 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, ippm@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20231031223718.DE54785414@rfcpa.amsl.com>
Date: Tue, 31 Oct 2023 15:37:18 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/eZYbolqPdWS_X1udQG-pzxPm934>
Subject: [ippm] RFC 9506 on Explicit Host-to-Network Flow Measurements Techniques
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Oct 2023 22:37:40 -0000

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

        
        RFC 9506

        Title:      Explicit Host-to-Network Flow Measurements Techniques 
        Author:     M. Cociglio,
                    A. Ferrieux,
                    G. Fioccola,
                    I. Lubashev,
                    F. Bulgarella,
                    M. Nilo,
                    I. Hamchaoui,
                    R. Sisto
        Status:     Informational
        Stream:     IETF
        Date:       October 2023
        Mailbox:    mauro.cociglio@outlook.com,
                    alexandre.ferrieux@orange.com,
                    giuseppe.fioccola@huawei.com,
                    ilubashe@akamai.com,
                    fabio.bulgarella@guest.telecomitalia.it,
                    massimo.nilo@telecomitalia.it,
                    isabelle.hamchaoui@orange.com,
                    riccardo.sisto@polito.it
        Pages:      37
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ippm-explicit-flow-measurements-07.txt

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

        DOI:        10.17487/RFC9506

This document describes protocol-independent methods called Explicit
Host-to-Network Flow Measurement Techniques that can be applicable to
transport-layer protocols between the client and server. These
methods employ just a few marking bits inside the header of each
packet for performance measurements and require the client and server
to collaborate. Both endpoints cooperate by marking packets and,
possibly, mirroring the markings on the round-trip connection. The
techniques are especially valuable when applied to protocols that
encrypt transport headers since they enable loss and delay
measurements by passive, on-path network devices. This document
describes several methods that can be used separately or jointly
depending of the availability of marking bits, desired measurements,
and properties of the protocol to which the methods are applied.

This document is a product of the IP Performance Measurement Working Group of the IETF.


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
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

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