BGP Extension for Advertising In-situ Flow Information Telemetry (IFIT) Capabilities
draft-wang-idr-bgp-ifit-capabilities-01

Document Type Active Internet-Draft (individual)
Authors Yali Wang  , Shunwan Zhuang  , Yunan Gu 
Last updated 2020-10-27
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)
Network Working Group                                            Y. Wang
Internet-Draft                                                 S. Zhuang
Intended status: Standards Track                                   Y. Gu
Expires: May 1, 2021                                              Huawei
                                                        October 28, 2020

BGP Extension for Advertising In-situ Flow Information Telemetry (IFIT)
                              Capabilities
                draft-wang-idr-bgp-ifit-capabilities-01

Abstract

   This document defines extensions to BGP to advertise the In-situ Flow
   Information Telemetry (IFIT) capabilities.  Within an IFIT domain,
   IFIT-capability advertisement from the tail node to the head node
   assists the head node to determine whether a particular IFIT Option
   type can be encapsulated in data packets.  Such advertisement would
   be useful for mitigating the leakage threat and facilitating the
   deployment of IFIT measurements on a per-service and on-demand basis.

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 May 1, 2021.

Wang, et al.               Expires May 1, 2021                  [Page 1]
Internet-Draft           BGP for IFIT Capability            October 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.  Definitions and Acronyms  . . . . . . . . . . . . . . . . . .   3
   3.  IFIT Capabilities . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Option 1: Extension to BGP Extended Community for IFIT-
       Capability Advertisement  . . . . . . . . . . . . . . . . . .   4
     4.1.  IPv4-Address-Specific IFIT Extended Community . . . . . .   4
     4.2.  IPv6-Address-Specific IFIT Extended Community . . . . . .   5
   5.  Option 2: Extension to BGP Next-Hop Capability for IFIT-
       Capability Advertisement  . . . . . . . . . . . . . . . . . .   6
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   8.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   7
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   8
     10.2.  Informative References . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   In-situ Flow Information Telemetry (IFIT) denotes a family of flow-
   oriented on-path telemetry techniques, including In-situ OAM (IOAM)
   [I-D.ietf-ippm-ioam-data] and Alternate Marking [RFC8321], which can
   provide flow information on the entire forwarding path on a per-
   packet basis in real time (e.g., jitter, latency, packet loss).

   The IFIT model describes how service flows are measured to obtain
   packet loss and latency.  Specifically, IFIT measures the packet loss
   and latency of service flows on the ingress and egress of the transit
   network, and summarizes desired performance indicators.  The IFIT
   model is composed of three objects: target flow, transit network, and

Wang, et al.               Expires May 1, 2021                  [Page 2]
Internet-Draft           BGP for IFIT Capability            October 2020

   measurement system.  The transit network only bears target flows.
Show full document text