A One-Path Congestion Metric for IPPM
draft-dang-ippm-congestion-02

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02

Network Working Group                                       D. Dang, Ed.
Internet-Draft                                                    Huawei
Intended status: Informational                                   W. Wang
Expires: May 7, 2020                                       China Telecom
                                                                  W. LEE
                                                                   LG U+
                                                                  W. Yan
                                                                 Tencent
                                                        November 4, 2019

                 A One-Path Congestion Metric for IPPM
                     draft-dang-ippm-congestion-02

Abstract

   This memo defines a metric for one path congestion across Internet
   paths.  The traditional mode evaluates network congestion based on
   the bandwidth utilization of the link.  However, there is a lack of
   E2E path congestion that is truly service oriented.  So A Path
   Congestion Metric is required.

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 May 7, 2020.

Copyright Notice

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

   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

Dang, et al.               Expires May 7, 2020                  [Page 1]
Internet-Draft      A Path Congestion Metric for IPPM      November 2019

   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
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
     1.2.  Terminology & Abbreviations . . . . . . . . . . . . . . .   3
     1.3.  Motivation  . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  A singleton definition of a Type-P-Path-Congestion Metric . .   4
     2.1.  Metric Name . . . . . . . . . . . . . . . . . . . . . . .   4
     2.2.  Metric Parameters . . . . . . . . . . . . . . . . . . . .   4
     2.3.  Metric unit . . . . . . . . . . . . . . . . . . . . . . .   5
     2.4.  Definition  . . . . . . . . . . . . . . . . . . . . . . .   5
     2.5.  Methodologies . . . . . . . . . . . . . . . . . . . . . .   5
     2.6.  Reporting the Metric  . . . . . . . . . . . . . . . . . .   7
   3.  A Definition for Samples of Path Congestion . . . . . . . . .   7
     3.1.  Metric Name . . . . . . . . . . . . . . . . . . . . . . .   7
     3.2.  Metric Parameters . . . . . . . . . . . . . . . . . . . .   7
     3.3.  Metric Units  . . . . . . . . . . . . . . . . . . . . . .   8
     3.4.  Definition  . . . . . . . . . . . . . . . . . . . . . . .   8
     3.5.  Methodologies . . . . . . . . . . . . . . . . . . . . . .   8
     3.6.  Reporting the Metric  . . . . . . . . . . . . . . . . . .   9
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   9
   7.  Normative References  . . . . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   As we know, the current network has been already being in load
   balancing mode, however it is partially congested.  To solve the
   problem of unbalanced network load[draft-liu-ican], Congestion of
   paths requires an assessment metric.  The traditional mode evaluates
   network congestion based on the bandwidth utilization of the link.
   However, there is a lack of E2E path congestion that is truly service
   oriented.

   So this memo defines a metric for a path congestion across Internet
   paths.  Currently there is no path congestion metric specified
   according to [RFC2330] framework, so the notions and conventions of