Structured Flow Label
draft-filsfils-6man-structured-flow-label-00

Document Type Active Internet-Draft (individual)
Authors Clarence Filsfils  , Ahmed Abdelsalam  , Shay Zadok  , Xiaohu Xu  , Weiqiang Cheng  , Dani Voyer  , Pablo Camarillo 
Last updated 2021-03-16
Stream (None)
Intended RFC status (None)
Formats plain text xml 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)
6man                                                    C. Filsfils, Ed.
Internet-Draft                                        A. Abdelsalam, Ed.
Updates: 6437 (if approved)                          Cisco Systems, Inc.
Intended status: Standards Track                                S. Zadok
Expires: September 17, 2021                                     Broadcom
                                                                   X. Xu
                                                           Capitalonline
                                                                W. Cheng
                                                            China Mobile
                                                                D. Voyer
                                                             Bell Canada
                                                            P. Camarillo
                                                     Cisco Systems, Inc.
                                                          March 16, 2021

                         Structured Flow Label
              draft-filsfils-6man-structured-flow-label-00

Abstract

   This document defines the IPv6 Structured Flow Label.  The seamless
   nature of the change to [RFC6437] is demonstrated.  Benefits of the
   solution are explained.  Use-cases are illustrated.

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 September 17, 2021.

Copyright Notice

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

Filsfils, et al.       Expires September 17, 2021               [Page 1]
Internet-Draft            Structured Flow Label               March 2021

   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.  Structured Flow Label Format  . . . . . . . . . . . . . . . .   3
   3.  Recommended Design  . . . . . . . . . . . . . . . . . . . . .   4
   4.  Seamless Migration from RFC6437 . . . . . . . . . . . . . . .   5
   5.  Benefits  . . . . . . . . . . . . . . . . . . . . . . . . . .   6
   6.  IPv6 End-to-End Absolute Loss Measurements  . . . . . . . . .   6
   7.  Programmed Sampling of packets  . . . . . . . . . . . . . . .   7
   8.  Postcard-based Telemetry using packet Marking (PBT-M) . . . .   8
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   9
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   9
     10.2.  Informative References . . . . . . . . . . . . . . . . .  10
   Appendix A.  Entropy  . . . . . . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   The IPv6 header [RFC8200] contains a 20-bit field called "Flow Label"
   (FL) where the left-most bit is number 19 and the right-most bit is
   number0.

                      1                   0
    9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             Flow Label                |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
           Figure 1: IPv6 Flow Label

   The FL usage is specified in [RFC6437], briefly for entropy purpose.

   Instead of using FL as a single 20-bit entropy structure, this
   document updates [RFC6437] and defines the 20-bit FL field as a
   structure of two fields:

   o  FLC: 4-bit per-packet control bits for generic application marking
      (e.g., group-based policy)

Filsfils, et al.       Expires September 17, 2021               [Page 2]
Internet-Draft            Structured Flow Label               March 2021

   o  FLE: 16-bit per-flow entropy (equivalent to [RFC6437] definition)

   This document shows that updating [RFC6437] is a seamless migration
Show full document text