2. Terminology

この節では IPFIX delay performance metric export の RFC テキストを保持し, On-Path Telemetry, OAM nodes, Flow Records, performance metric IDs 27-30, IPFIX Information Elements 530-533, IANA registrations, operational guidance, encoding examples を扱う.

RFC 原文

2.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in
   BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

   This document defines the following terms:

   OAM Header Encapsulating Node:
      Receives the IP packets, encapsulates the packets with an OAM
      header, and adds the timestamp into the OAM header.

   OAM Header Transit Node:
      Receives the IP packets, then measures the delay between the
      timestamp in the packet and the timestamp when the packet was
      received.

   OAM Header Decapsulating Node:
      Receives the IP packets, computes the delay between the timestamp
      in the packet and the timestamp when the packet was received, and
      removes the OAM header from the packet.

   This document makes use of the terms defined in [RFC7011], [RFC8911]
   and [RFC7799].

   The following terms are used as defined in [RFC7011]:

   *  Collector

   *  Exporter

   *  Flow

   *  Flow Record

   *  IPFIX

   *  IPFIX Information Elements (IEs)

   *  Observation Point

   The following terms are used as defined in [RFC8911]:

   *  Performance Metric

   *  Performance Metrics Registry

   *  Registered Performance Metric

   The following term is used as defined in Section 3.8 of [RFC7799]:

   *  Hybrid Type I