In-situ Flow Information Telemetry (IFIT) Node Capability Advertisement
draft-wang-lsr-ifit-node-capability-advertisement-00

Document Type Active Internet-Draft (individual)
Last updated 2020-03-22
Replaces draft-wang-idr-bgp-ls-ifit-node-capability, draft-liu-lsr-isis-ifit-node-capability, draft-wang-lsr-ospf-ifit-node-capability
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf 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)
Link State Routing Working Group                                 Y. Wang
Internet-Draft                                                   T. Zhou
Intended status: Standards Track                                  M. Liu
Expires: September 24, 2020                                       Huawei
                                                                 R. Pang
                                                            China Unicom
                                                          March 23, 2020

In-situ Flow Information Telemetry (IFIT) Node Capability Advertisement
          draft-wang-lsr-ifit-node-capability-advertisement-00

Abstract

   For advertising In-situ Flow Information Telemetry (IFIT) node
   capabilities within the entire routing domain, this document extends
   a new optional TLV to the OSPF RI Opaque LSA, a new optional sub-TLV
   to the IS-IS Router CAPABILITY TLV, and a new Node Attribute TLV that
   is encoded in the BGP-LS attribute with Node NLRIs to carry IFIT node
   capabilities information.  Such advertisement allows entities (e.g. a
   centralized controller) to determine whether a particular IFIT
   functionality can be supported in a given network.

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.

Wang, et al.           Expires September 24, 2020               [Page 1]
Internet-Dradraft-wang-lsr-ifit-node-capability-advertisemen  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.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  IFIT Node Capability Advertisement  . . . . . . . . . . . . .   3
     3.1.  IFIT Node Capability Information  . . . . . . . . . . . .   3
     3.2.  OSPF Extension IFIT Node Capability TLV . . . . . . . . .   5
     3.3.  IS-IS Extension IFIT Node Capability Sub-TLV  . . . . . .   6
     3.4.  BGP-LS Extension IFIT Node Capability TLV . . . . . . . .   6
   4.  Application . . . . . . . . . . . . . . . . . . . . . . . . .   7
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   9
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   IFIT provides a complete framework architecture and a reflection-loop
   working solution for on-path flow telemetry
   [I-D.song-opsawg-ifit-framework].  At present, there are a family of
   emerging on-path flow telemetry techniques, 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], etc.  IFIT is a
   solution focusing on network domains.  The "network domain" consists
   of a set of network devices or entities within a single Atonomous
   System (AS).  The part of the network which employs IFIT is referred
   to as the IFIT domain.  One network domain may consist of multiple
   IFIT domains.  An IFIT domain may cross multiple network domains.
Show full document text