User Devices Explicit Monitoring
draft-cnbf-ippm-user-devices-explicit-monitoring-00

Document Type Active Internet-Draft (individual)
Authors Mauro Cociglio  , Massimo Nilo  , Fabio Bulgarella  , Giuseppe Fioccola 
Last updated 2020-10-27
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
IPPM                                                         M. Cociglio
Internet-Draft                                                   M. Nilo
Intended status: Informational                             F. Bulgarella
Expires: April 30, 2021                             Telecom Italia (TIM)
                                                             G. Fioccola
                                                     Huawei Technologies
                                                        October 27, 2020

                    User Devices Explicit Monitoring
          draft-cnbf-ippm-user-devices-explicit-monitoring-00

Abstract

   This document describes a methodology to monitor network performance
   exploiting user devices.  This can be achieved using the Explicit
   Flow Measurement Techniques, protocol independent methods that employ
   few marking bits, inside the header of each packet, for loss and
   delay measurement.  User devices and servers, marking the traffic,
   signal these metrics to intermediate network observers allowing them
   to measure connection performance, and to locate the network segment
   where impairments happen.  In addition or in alternative to network
   observers, a probe can be installed on the user device with
   remarkable benefits in terms of hardware deployment and measurement
   scalability.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 30, 2021.

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Cociglio, et al.         Expires April 30, 2021                 [Page 1]
Internet-Draft              User Device Probe               October 2020

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Notational Conventions  . . . . . . . . . . . . . . . . . . .   2
   3.  Explicit Performance Open Issues  . . . . . . . . . . . . . .   3
   4.  Explicit Performance Probes on User Devices . . . . . . . . .   3
   5.  Device Owner Activates Explicit Performance Measurement . . .   3
   6.  Who Will Handle the Performance Data? . . . . . . . . . . . .   4
   7.  The Explicit Performance App  . . . . . . . . . . . . . . . .   4
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   9.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .   5
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   11. Change Log  . . . . . . . . . . . . . . . . . . . . . . . . .   5
   12. Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   5
   13. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   14. References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     14.1.  Normative References . . . . . . . . . . . . . . . . . .   5
     14.2.  Informative References . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   Explicit Performance Monitoring enables a passive observer (a probe)
   to measure delay and loss just watching the marking (a few header
   bits) of live traffic packets.  It works on client-server protocols:
   e.g.  QUIC [QUIC-TRANSPORT], TCP [TCP].  The different methods are
   described in [EXPLICIT-FLOW-MEASUREMENTS].

   This document explains how to employ the methods described in
   [EXPLICIT-FLOW-MEASUREMENTS] by proposing the user device as a
   convenient place for the Explicit Performance Observer.

2.  Notational Conventions

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

Cociglio, et al.         Expires April 30, 2021                 [Page 2]
Show full document text