[OPSAWG] Comments for draft-song-opsawg-ifit-framework-05.txt

<daniel@olddog.co.uk> Tue, 08 October 2019 07:47 UTC

Return-Path: <dk@danielking.net>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 962B41200F8 for <opsawg@ietfa.amsl.com>; Tue, 8 Oct 2019 00:47:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.647
X-Spam-Level:
X-Spam-Status: No, score=-1.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=danielking-net.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XlTFJ-zgKfIg for <opsawg@ietfa.amsl.com>; Tue, 8 Oct 2019 00:47:42 -0700 (PDT)
Received: from mail-wr1-x42a.google.com (mail-wr1-x42a.google.com [IPv6:2a00:1450:4864:20::42a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D28A1200D5 for <opsawg@ietf.org>; Tue, 8 Oct 2019 00:47:42 -0700 (PDT)
Received: by mail-wr1-x42a.google.com with SMTP id j11so12341457wrp.1 for <opsawg@ietf.org>; Tue, 08 Oct 2019 00:47:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=danielking-net.20150623.gappssmtp.com; s=20150623; h=sender:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding:thread-index:content-language; bh=h5x4IRK6sqkD+hrSKaCZXWZPc38KaWitxbSyPNwD8ks=; b=zXvU4OzKxoUQ3ZuA1tdcuDFbv8TzCi2BLdhmwrIC2ChwVlrAZXs60+YSj+uoA7DAi/ F+Q4T3Huc3I+fRToAgejk3Ajb5GRCMht40067Dw6BPxT+0nUoo93binGtc/HKzt0saqO 62VtMrV5cFJib5p06IGkqbfFU+ZM6V37hJchNVMk7LeKVL1zImjHXE0lQgi5flC/vDhE UJ+CjeHnR+57EdLnaMr1ySR5+l6NWaLDhu7ubWAMihkIqkfVnL4vQKLI2BBPYxMz3/Yi Hxvfv13L/FdXh7/vBELVVXNVp+Mp1Z31T6bs+FUXE3eE5Mosa80ht4DD3R8SuVniBUSA NHDQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:to:cc:subject:date:message-id :mime-version:content-transfer-encoding:thread-index :content-language; bh=h5x4IRK6sqkD+hrSKaCZXWZPc38KaWitxbSyPNwD8ks=; b=e1jU4WtR9tJAA46Fui9ZxBzd0hgz0zYNo1IwVqgXJ3O1+MeV26zd77tmMCz5jFmD2A yl0rE2LyX14W1ffvyDcWtmJicRYcqIOr7INkht4u7k/a7LiQ1+HVR7p3leimZIw1Ex0F KpDCzplxWAl3NZmX3Znl1cSY5gekYpMRHeusTPDD9M8ehyLYWBpHqLkCpgm1UDSL+KEO 9XRNjU4NV5sYFYBq+2BqTryzbpgQ/6hnXm/tVg4iIdivEfgVJmHtUkvTsH8erWfi3UR8 b1wjOUP3DzdZH3ayhYzxlUOFlHAC4q92MpuAJSKlgrpQtNskLWvAAHJ++iE2uEi1c+MR kKiQ==
X-Gm-Message-State: APjAAAVSTKhyLhamRqzOVN0mcBKMKyHYNvE9TRO76Bt6Un7km+OeaSNa 3K4hssmAZs50/Fy89imQBx7Sww==
X-Google-Smtp-Source: APXvYqxeKS1RXJius/8kBMBRG9rpC7uQXA/dMJC/rxygFc7HUkocAmsg6CdYX7Wkg/H4fnlMYk+iIg==
X-Received: by 2002:adf:e610:: with SMTP id p16mr14593651wrm.313.1570520859116; Tue, 08 Oct 2019 00:47:39 -0700 (PDT)
Received: from INARA (host81-150-64-4.in-addr.btopenworld.com. [81.150.64.4]) by smtp.gmail.com with ESMTPSA id h17sm5062269wme.6.2019.10.08.00.47.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 08 Oct 2019 00:47:38 -0700 (PDT)
Sender: Daniel King <dk@danielking.net>
X-Google-Original-Sender: "Daniel King" <dk@danielking.net>
From: daniel@olddog.co.uk
To: opsawg@ietf.org
Cc: draft-song-opsawg-ifit-framework.authors@ietf.org
Date: Tue, 08 Oct 2019 08:48:12 +0100
Message-ID: <036b01d57dac$bcdc0380$36940a80$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdV9q4Ma1oGEdyHoSeiqNjOLPJoZ3A==
Content-Language: en-gb
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/5NKJN_hv671e-Zn-ulljRJE5qms>
Subject: [OPSAWG] Comments for draft-song-opsawg-ifit-framework-05.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Oct 2019 07:47:45 -0000

Dear Authors,

Please find some comments, thoughts and suggestions for
https://tools.ietf.org/html/draft-song-opsawg-ifit-framework-05

Overall, a really useful document and something I hope the WG can progress.
There are many in-band/in-situ OAM documents currently floating around in at
least four IETF WGs, so a document that helps coordinate the discussion
would be very valuable. 

General Comments

(1) Abstract - The scope is clear, but the intention of this document could
be clarified. You might rephrase as:

>>
   For efficient network operation, most operators rely on traditional
   Operation, Administration and Maintenance (OAM) methods, which 
   include proactive and reactive techniques, running in active and 
   passive modes. As networks increase in scale they become more 
   susceptible to hardware and software failures, and misconfiguration
   errors. 

   With the advent of programmable data-plane emerging "on-path" OAM
   techniques, such as flow telemetry,  provide unprecedented insight
   and fast notification of network issues (e.g., jitter, increased 
   latency, packet loss, significant bit error variations, and unequal
   load-balancing. 

   In-situ Flow Information Telemetry (iFIT), would provide a method 
   for efficiently applying underlying on-path flow telemetry 
   techniques, applicable across various network environments. 

   This document outlines an iFIT framework, which enumerates several
   critical functional components and describes how these components
   are assembled together to achieve a complete and closed-loop 
   working solution for on-path flow telemetry. 
<<

(2) Use of "Application-aware network" - We may need to be careful with this
the usage of this word. It already has a well-used meaning in the context of
Cloud and SDN. If you are happy with the general description, we could
continue to use "application-aware networking", but we should add a
definition, such as:

>>
   Future networks must also support application-aware networking. 
   Application-aware networking is an emerging industry term and 
   typically used to describe the capacity of an intelligent network to
   maintain current information about user and application connections 
   that use network resources and, as a result, the operator is able to 
   optimize the network resource usage and monitoring to ensure 
   application and traffic optimality.  <<

(3) Additional Challenge - Have you considered a model-driven telemetry API
from the iFIT framework that could expose network performance to external
applications? Maybe something along the lines of:

>>
   o  C6: Development of simplified iFIT telemetry primitives and model, 
      including: telemetry data (e.g., nodes, links, ports, paths, flows, 
      timestamps) query primitives. These may be used by an API-based 
      telemetry service for external applications to iFIT, for 
      monitoring end-to-end latency measurement of 
      network paths and application latency calculation via the iFIT 
      framework. 
<<      

(4) Security - I think this section requires significantly more text as I
can think of numerous issues that will need to be considered, or at least
highlighting  best practices and considerations discussed in other
documents. I started working on a much more comprehensive security section,
I will send this to the authors directly (or the list if you prefer) over
the next few days. 

(5) Please find the edits, typos, NITs, suggested text in the attached
documents: 

o draft-song-opsawg-ifit-framework-05-review.txt -
https://github.com/danielkinguk/draft-song-opsawg-ifit-framework/blob/master
/draft-song-opsawg-ifit-framework-05-review.txt
o draft-song-opsawg-ifit-framework-05-review-diff.html -
https://github.com/danielkinguk/draft-song-opsawg-ifit-framework/blob/master
/draft-song-opsawg-ifit-framework-05-review-diff.html

I hope this helps. 
BR, Dan. 

-----Original Message-----
From: I-D-Announce <i-d-announce-bounces@ietf.org> On Behalf Of
internet-drafts@ietf.org
Sent: 26 September 2019 18:29
To: i-d-announce@ietf.org
Subject: I-D Action: draft-song-opsawg-ifit-framework-05.txt


A New Internet-Draft is available from the on-line Internet-Drafts
directories.


        Title           : In-situ Flow Information Telemetry Framework
        Authors         : Haoyu Song
                          Zhenbin Li
                          Tianran Zhou
                          Fengwei Qin
                          Huanan Chen
                          Jaewhan Jin
                          Jongyoon Shin
	Filename        : draft-song-opsawg-ifit-framework-05.txt
	Pages           : 16
	Date            : 2019-09-26

Abstract:
   Unlike the existing active and passive OAM techniques, the emerging
   on-path flow telemetry techniques provide unmatched visibility into
   user traffic, showing great application potential not only for
   today's network OAM but also for future's automatic network
   operation.  Summarizing the current industry practices that addresses
   the deployment challenges and application requirements, we provide a
   closed-loop framework, named In-situ Flow Information Telemetry
   (iFIT), for efficiently applying a family of underlying on-path flow
   telemetry techniques in various network environments.  The framework
   enumerates several key architectural components and describes how
   these components are assembled together to achieve a complete and
   closed-loop working solution for on-path flow telemetry.  Following
   such a framework allows better scalability, fosters application
   innovations, and promotes both vertical and horizontal
   interoperability.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-song-opsawg-ifit-framework/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-song-opsawg-ifit-framework-05
https://datatracker.ietf.org/doc/html/draft-song-opsawg-ifit-framework-05

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-song-opsawg-ifit-framework-05


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html or
ftp://ftp.ietf.org/ietf/1shadow-sites.txt