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

Haoyu Song <haoyu.song@futurewei.com> Tue, 08 October 2019 22:47 UTC

Return-Path: <haoyu.song@futurewei.com>
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 B6D7C1201AA; Tue, 8 Oct 2019 15:47:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=futurewei.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 yNCKbnMjtE5J; Tue, 8 Oct 2019 15:47:35 -0700 (PDT)
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-eopbgr750133.outbound.protection.outlook.com [40.107.75.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 35479120289; Tue, 8 Oct 2019 15:47:35 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=hZfZfYriuUjpHc4bpKHW8Ka4zNsxRCs0gKcJ8awweB5ZmEpf/8fS5P0kijdH2/439m4RjoUvqMUh3GmCd/Y4HImUEHq8CzQX9zRt3OVptW1n3w9lODcIxIg+7vN5Ys8p+nU/LQ8x/+ijdMgWEeXqj9F7f2lerrAlBUu61pRfu5+gaK8KMDHeIjwAIg3R1lGywicIUUv+phU40pfkOJY+HDH5jdtuD5iCE2dnS2e126Sede0NDNd+omr+JtHAky2ZNimGh5pwsFc62Zf59Z6SdJTfha2tiN4tNkBYJXV0cwgV365+0Y4GpE2pI0yxea+7+U8BWPj0AlwSdc6E1s5Bbg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=1O9Wruqc0dQAah8mRwSlvK4r2Eb7RYnKBQvbm+cfodk=; b=PcwJqqdKR5eLZB02JjZV/5fZzcm7FSJm1ChB64um8S5ejKzHvBSPbLnskL+uKeoW7wB+zCJr32WOEbDBKimnQNqip2NCWYvRd5hQE8aSzCujqU5T4Jc8urw7TQ93qfVsQHJgyoG6sy17t4PMjkjKN55WSQStjiQdLggBDCfxsX5YlytURBG6Byqp0GaTguTjkVyYJ/wIV6EnFS32Qz4++GPjxY/20kaIP7ZeWhGflgCp7lFtOgWbuC6bJQVmSJSwVP3KNgnScjkviBtVybsIRBCXuWonEWEKMbBWGAZPlj4rB4C5HWdagjnrK/TIXPnunU4VUdTv3fgLz25ZMYdMVA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=futurewei.com; dmarc=pass action=none header.from=futurewei.com; dkim=pass header.d=futurewei.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=1O9Wruqc0dQAah8mRwSlvK4r2Eb7RYnKBQvbm+cfodk=; b=diKuIjwFsllWSgiu6Rqi4f1nRoelmLVadfnyS2irva6yQ/YYC43kRGHEalg3ynoUikpDrawsQPgnHDz6z49OKfoAY/526LWE9YZuIZgclfGyKI7S6rVG1Epm7baiItUFEFvKmmWegSILBsFqe/16sQrUGRjOBGEAY+WGMcrO1sw=
Received: from MN2PR13MB3582.namprd13.prod.outlook.com (10.255.239.156) by MN2PR13MB2670.namprd13.prod.outlook.com (20.178.251.213) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2347.14; Tue, 8 Oct 2019 22:47:32 +0000
Received: from MN2PR13MB3582.namprd13.prod.outlook.com ([fe80::6dcb:88a5:b3a9:e05c]) by MN2PR13MB3582.namprd13.prod.outlook.com ([fe80::6dcb:88a5:b3a9:e05c%4]) with mapi id 15.20.2347.016; Tue, 8 Oct 2019 22:47:32 +0000
From: Haoyu Song <haoyu.song@futurewei.com>
To: "daniel@olddog.co.uk" <daniel@olddog.co.uk>, "opsawg@ietf.org" <opsawg@ietf.org>
CC: "draft-song-opsawg-ifit-framework.authors@ietf.org" <draft-song-opsawg-ifit-framework.authors@ietf.org>
Thread-Topic: [OPSAWG] Comments for draft-song-opsawg-ifit-framework-05.txt
Thread-Index: AdV9q4Ma1oGEdyHoSeiqNjOLPJoZ3AAfqBYA
Date: Tue, 08 Oct 2019 22:47:32 +0000
Message-ID: <MN2PR13MB35823C18402F15D6A6454B359A9A0@MN2PR13MB3582.namprd13.prod.outlook.com>
References: <036b01d57dac$bcdc0380$36940a80$@olddog.co.uk>
In-Reply-To: <036b01d57dac$bcdc0380$36940a80$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=haoyu.song@futurewei.com;
x-originating-ip: [12.111.81.80]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 2865e0e1-69a3-486b-67e5-08d74c41814f
x-ms-traffictypediagnostic: MN2PR13MB2670:
x-ms-exchange-purlcount: 8
x-microsoft-antispam-prvs: <MN2PR13MB2670E297791B95887A4608699A9A0@MN2PR13MB2670.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-forefront-prvs: 01842C458A
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(39850400004)(396003)(346002)(376002)(366004)(136003)(199004)(189003)(13464003)(53484002)(469094003)(2906002)(11346002)(186003)(305945005)(76116006)(81166006)(7736002)(2501003)(8676002)(8936002)(64756008)(86362001)(66446008)(66476007)(66556008)(81156014)(52536014)(74316002)(33656002)(6306002)(9686003)(55016002)(66066001)(44832011)(6246003)(26005)(229853002)(446003)(486006)(66946007)(99286004)(102836004)(476003)(5660300002)(7696005)(6116002)(53546011)(6506007)(66574012)(3846002)(76176011)(256004)(6436002)(71190400001)(71200400001)(110136005)(4326008)(5024004)(45080400002)(25786009)(478600001)(14444005)(966005)(316002)(14454004); DIR:OUT; SFP:1102; SCL:1; SRVR:MN2PR13MB2670; H:MN2PR13MB3582.namprd13.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: futurewei.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: +nixuxaokYhRi1jzgZwZIDGd+fdfm2KGVTE46/2md+tAsri1yjC/yjz7WvjsJIpBrz+q7B1j1cIOyDxX2RuHTk4y09/UGm8wJa1V6ilS4vDME6bVg8Egdg/bC/ybvgdQY9MdbDi53cU69dsGG+i9AulKShDhOa8U/GWFIZdXw/n0VGbMElQZ+3mSRFi1yJsjwKUsNN4c/Z0TKJa61g6ZJYjus7ZgVPFTx40PYvrk6VqOONhVV5UexRbBbqvw4WRBomru+LqH8vktRY5y6P3zas5rjmAzg1tDqnn92Yy77PCxwQ+u3Dfc9CWh9Mlmy5c5nXgSyEgK5JQLIhGTdmH6PGH79qqfqHbPDFEP2YDBKAY7j3uQM2EOojuiFRhpV038a81qz9rk3arb+Kx4NNh8D0IhnenMqQ6nKCEAjZivNlCgsOeCQndAqpe0fXINvc5/PADxAe17GWrQGfLs/kxVow==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 2865e0e1-69a3-486b-67e5-08d74c41814f
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Oct 2019 22:47:32.1325 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: BNZSftgcB6X7h+DCNdayT+/KdQNZhRbks2xp2Tu4dSiRjXo3omYlVUYHxv2Nt7omhcP7cGSUCleDSEJuJNnc7A==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR13MB2670
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/_kkfBFVewMbOEnBniWVWAEUjuFE>
Subject: Re: [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 22:47:46 -0000

Hi Daniel,

Thank you very much for your review! Your suggestions will be considered in the next revision of the draft.

Best regards,
Haoyu

-----Original Message-----
From: OPSAWG <opsawg-bounces@ietf.org> On Behalf Of daniel@olddog.co.uk
Sent: Tuesday, October 08, 2019 12:48 AM
To: opsawg@ietf.org
Cc: draft-song-opsawg-ifit-framework.authors@ietf.org
Subject: [OPSAWG] Comments for draft-song-opsawg-ifit-framework-05.txt

Dear Authors,

Please find some comments, thoughts and suggestions for
https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-song-opsawg-ifit-framework-05&amp;data=02%7C01%7Chaoyu.song%40futurewei.com%7Cf4f7a57161ce480043f008d74bc3e46c%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637061177051023095&amp;sdata=zQGoZucgrTGuHKS0M2H5bUF%2F%2Fqr6kbN%2B9h0ZnQWtKwk%3D&amp;reserved=0

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://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdanielkinguk%2Fdraft-song-opsawg-ifit-framework%2Fblob%2Fmaster&amp;data=02%7C01%7Chaoyu.song%40futurewei.com%7Cf4f7a57161ce480043f008d74bc3e46c%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637061177051023095&amp;sdata=MKuRxT18X8EY%2BiuQ6y1eiB8G9n4mT1XVkJvvaq3AYME%3D&amp;reserved=0
/draft-song-opsawg-ifit-framework-05-review.txt
o draft-song-opsawg-ifit-framework-05-review-diff.html -
https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdanielkinguk%2Fdraft-song-opsawg-ifit-framework%2Fblob%2Fmaster&amp;data=02%7C01%7Chaoyu.song%40futurewei.com%7Cf4f7a57161ce480043f008d74bc3e46c%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637061177051023095&amp;sdata=MKuRxT18X8EY%2BiuQ6y1eiB8G9n4mT1XVkJvvaq3AYME%3D&amp;reserved=0
/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://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-song-opsawg-ifit-framework%2F&amp;data=02%7C01%7Chaoyu.song%40futurewei.com%7Cf4f7a57161ce480043f008d74bc3e46c%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637061177051023095&amp;sdata=tGinrvPEyB2d5Cb9eZE2HUPblxjEyW0Ej%2F9VLPIH%2F%2BA%3D&amp;reserved=0

There are also htmlized versions available at:
https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-song-opsawg-ifit-framework-05&amp;data=02%7C01%7Chaoyu.song%40futurewei.com%7Cf4f7a57161ce480043f008d74bc3e46c%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637061177051023095&amp;sdata=zQGoZucgrTGuHKS0M2H5bUF%2F%2Fqr6kbN%2B9h0ZnQWtKwk%3D&amp;reserved=0
https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-song-opsawg-ifit-framework-05&amp;data=02%7C01%7Chaoyu.song%40futurewei.com%7Cf4f7a57161ce480043f008d74bc3e46c%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637061177051023095&amp;sdata=wRFvnHU1BrLfN1PKr7dfBLFc07dG2fc%2FfuKKpZ0YMWI%3D&amp;reserved=0

A diff from the previous version is available at:
https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Frfcdiff%3Furl2%3Ddraft-song-opsawg-ifit-framework-05&amp;data=02%7C01%7Chaoyu.song%40futurewei.com%7Cf4f7a57161ce480043f008d74bc3e46c%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637061177051023095&amp;sdata=dHzyr3fAtL2ipwlX80Ppo%2FCm5OjQn%2BHtTc%2FDxjMFShA%3D&amp;reserved=0


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://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fi-d-announce&amp;data=02%7C01%7Chaoyu.song%40futurewei.com%7Cf4f7a57161ce480043f008d74bc3e46c%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637061177051023095&amp;sdata=UxHbAlLC%2F9llj1lt%2FkEmztCNpdogm%2B%2Bxlayw1FFKtso%3D&amp;reserved=0
Internet-Draft directories: https://nam03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.ietf.org%2Fshadow.html&amp;data=02%7C01%7Chaoyu.song%40futurewei.com%7Cf4f7a57161ce480043f008d74bc3e46c%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637061177051023095&amp;sdata=IgxxFOuX%2Fl0DD%2Fu%2Fmiqsn%2BQ0mRMWP%2BXJjl7J9H%2Fb8CI%3D&amp;reserved=0 or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fopsawg&amp;data=02%7C01%7Chaoyu.song%40futurewei.com%7Cf4f7a57161ce480043f008d74bc3e46c%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637061177051023095&amp;sdata=fSTqkuPTaO2ts2wksNO5k%2Fb3rMKN5D%2BW51RZPBqjgFM%3D&amp;reserved=0