BGP Flow Specification Extensions to Enable In-situ Flow Information Telemetry (IFIT)
draft-liu-idr-flowspec-ifit-04

Document Type Active Internet-Draft (individual)
Last updated 2020-03-23
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)
Interdomain Routing Working Group                                 M. Liu
Internet-Draft                                                   Y. Wang
Intended status: Standards Track                                  Huawei
Expires: September 24, 2020                                      R. Pang
                                                            China Unicom
                                                          March 23, 2020

  BGP Flow Specification Extensions to Enable In-situ Flow Information
                            Telemetry (IFIT)
                     draft-liu-idr-flowspec-ifit-04

Abstract

   BGP Flowspec mechanism propogates both traffic Flow Specifications
   and Traffic Filtering Actions by making use of the Border Gateway
   Protocol Network Layer Reachability Information (BGP NLRI) and the
   BGP Extended Community encoding formats.  In order to address the
   automatic deployment of IPv4 unicast and VPNv4 unicast on-path flow
   telemetry as well as IPv6 families, this document specifies a new BGP
   Extended Community named IFIT Action Specific Extended Community to
   distribute In-situ Flow Information Telemetry (IFIT) actions.

Requirements Language

   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 RFC 2119 [RFC2119].

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

Liu, et al.            Expires September 24, 2020               [Page 1]
Internet-Draft       draft-liu-idr-flowspec-ifit-04           March 2020

Copyright Notice

   Copyright (c) 2020 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
   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.  Terminologies . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Motivation  . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  IFIT Action Specific Extended Community . . . . . . . . . . .   4
     4.1.  IOAM Pre-allocated Trace Option sub-type  . . . . . . . .   5
     4.2.  IOAM Incremental Trace Option sub-type  . . . . . . . . .   6
     4.3.  IOAM DEX Option sub-type  . . . . . . . . . . . . . . . .   6
     4.4.  IOAM Edge-to-Edge Option sub-type . . . . . . . . . . . .   7
     4.5.  Enhanced Alternate Marking Option sub-type  . . . . . . .   8
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   9
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   At present, a family of on-path flow telemetry techniques referred in
   [I-D.song-opsawg-ifit-framework] are emerging, including In-situ OAM
   (IOAM) [I-D.ietf-ippm-ioam-data], Postcard-Based Telemetry (PBT)
   [I-D.song-ippm-postcard-based-telemetry], IOAM Direct Export (DEX)
   [I-D.ioamteam-ippm-ioam-direct-export], Enhanced Alternate Marking
   (EAM) [I-D.zhou-ippm-enhanced-alternate-marking]. we categorize these
   on-path telemetry echniques as the hybrid OAM type I according to the
   classification defined in [RFC7799].  These techniques provide flow
   information on the entire forwarding path on a per-packet basis in
   real time, which are useful for application-aware network operations
   not only in data center and enterprise networks but also in carrier
   networks which may cross multiple domains.  The data provided by on-
Show full document text