Re: [Idr] New Version Notification for draft-qin-idr-sr-policy-ifit-03.txt

Giuseppe Fioccola <giuseppe.fioccola@huawei.com> Mon, 28 September 2020 10:37 UTC

Return-Path: <giuseppe.fioccola@huawei.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A1803A0CA7; Mon, 28 Sep 2020 03:37:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 Z0gvU7pi7m0J; Mon, 28 Sep 2020 03:37:53 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 35BF93A0C9C; Mon, 28 Sep 2020 03:37:53 -0700 (PDT)
Received: from lhreml722-chm.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id C873ED3FD44BA271BBB6; Mon, 28 Sep 2020 11:37:50 +0100 (IST)
Received: from dggeme703-chm.china.huawei.com (10.1.199.99) by lhreml722-chm.china.huawei.com (10.201.108.73) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.1913.5; Mon, 28 Sep 2020 11:37:50 +0100
Received: from fraeml714-chm.china.huawei.com (10.206.15.33) by dggeme703-chm.china.huawei.com (10.1.199.99) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Mon, 28 Sep 2020 18:37:47 +0800
Received: from fraeml714-chm.china.huawei.com ([10.206.15.33]) by fraeml714-chm.china.huawei.com ([10.206.15.33]) with mapi id 15.01.1913.007; Mon, 28 Sep 2020 12:37:45 +0200
From: Giuseppe Fioccola <giuseppe.fioccola@huawei.com>
To: "Dongjie (Jimmy)" <jie.dong@huawei.com>, "idr@ietf.org" <idr@ietf.org>
CC: "draft-qin-idr-sr-policy-ifit@ietf.org" <draft-qin-idr-sr-policy-ifit@ietf.org>
Thread-Topic: New Version Notification for draft-qin-idr-sr-policy-ifit-03.txt
Thread-Index: AQHWgP0+wPa8XQhwQk2KFGrYdbJCC6lU+4kwgCd6FaCAAYjncA==
Date: Mon, 28 Sep 2020 10:37:45 +0000
Message-ID: <e8356ac476534859bbd586136269d305@huawei.com>
References: <159903280992.25091.5278946449904193569@ietfa.amsl.com> <cc22287d5d3a4398af4818a2dd7a068d@huawei.com> <55226955c0a3414d842e7b33e9fb9c35@huawei.com>
In-Reply-To: <55226955c0a3414d842e7b33e9fb9c35@huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.48.216.15]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/DXUCAnSqnGFN515hWj62_VBIZvk>
Subject: Re: [Idr] New Version Notification for draft-qin-idr-sr-policy-ifit-03.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Sep 2020 10:37:56 -0000

Hi Jie,
Thanks a lot for your review.
Please find my answers inline tagged as [GF].

Regards,

Giuseppe

-----Original Message-----
From: Dongjie (Jimmy) 
Sent: Sunday, September 27, 2020 12:53 PM
To: Giuseppe Fioccola <giuseppe.fioccola@huawei.com>om>; idr@ietf.org
Cc: draft-qin-idr-sr-policy-ifit@ietf.org
Subject: RE: New Version Notification for draft-qin-idr-sr-policy-ifit-03.txt

Hi Giuseppe, 

Thanks for this update, here are some review comments from my side:

1. This document defines several sub-TLVs under BGP Tunnel Encapsulation Attribute for different IFIT related functions. Perhaps it would be better to define just one sub-TLV for IFIT, then define the different IFIT functions with sub-sub-TLVs?
[GF]: Yes, I agree. We can clarify that the 5 sub-TLVs (IOAM and AltMark) are carried in the IFIT sub-TLV. The new general IFIT attributes sub-TLV will be introduced in the next revision.

2. In addition to describing the encoding of the sub-TLVs, it may be helpful to also describe the operation of node when receiving an SR policy with these IFIT sub-TLVs.
[GF]: Good suggestion, we can also add a new section about the operations with IFIT similarly to the section on SR Policy Operations of draft-ietf-idr-segment-routing-te-policy. We will describe how the addition of IFITAttributes Sub-TLVs is handled for the SR Policy NLRI.

Best regards,
Jie

> -----Original Message-----
> From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Giuseppe Fioccola
> Sent: Wednesday, September 2, 2020 4:01 PM
> To: idr@ietf.org
> Cc: draft-qin-idr-sr-policy-ifit@ietf.org
> Subject: [Idr] FW: New Version Notification for 
> draft-qin-idr-sr-policy-ifit-03.txt
> 
> Dear All,
> We have just uploaded a new version of draft-qin-idr-sr-policy-ifit.
> This revision addresses the comments received during the IDR session 
> at IETF
> 108 from Ketan and Joel.
> In particular we tried to clarify the term IFIT and we also included a 
> new Motivation Section.
> 
> Feedbacks and suggestions are always welcome.
> 
> Best Regards,
> 
> Giuseppe
> 
> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Sent: Wednesday, September 2, 2020 9:47 AM
> To: Giuseppe Fioccola <giuseppe.fioccola@huawei.com>om>; Fengwei Qin 
> <qinfengwei@chinamobile.com>om>; wangyali <wangyali11@huawei.com>om>; Hang 
> Yuan <yuanhang@unionpay.com>om>; Tianran Zhou <zhoutianran@huawei.com>
> Subject: New Version Notification for 
> draft-qin-idr-sr-policy-ifit-03.txt
> 
> 
> A new version of I-D, draft-qin-idr-sr-policy-ifit-03.txt
> has been successfully submitted by Giuseppe Fioccola and posted to the 
> IETF repository.
> 
> Name:		draft-qin-idr-sr-policy-ifit
> Revision:	03
> Title:		BGP SR Policy Extensions to Enable IFIT
> Document date:	2020-09-02
> Group:		Individual Submission
> Pages:		13
> URL:
> https://www.ietf.org/internet-drafts/draft-qin-idr-sr-policy-ifit-03.txt
> Status:         https://datatracker.ietf.org/doc/draft-qin-idr-sr-policy-ifit/
> Htmlized:       https://tools.ietf.org/html/draft-qin-idr-sr-policy-ifit-03
> Htmlized:
> https://datatracker.ietf.org/doc/html/draft-qin-idr-sr-policy-ifit
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-qin-idr-sr-policy-ifit-03
> 
> Abstract:
>    Segment Routing (SR) policy is a set of candidate SR paths consisting
>    of one or more segment lists and necessary path attributes.  It
>    enables instantiation of an ordered list of segments with a specific
>    intent for traffic steering.  In-situ Flow Information Telemetry
>    (IFIT) refers to network OAM data plane on-path telemetry techniques,
>    in particular the most popular are In-situ OAM (IOAM) and Alternate
>    Marking.  This document defines extensions to BGP to distribute SR
>    policies carrying IFIT information.  So that IFIT methods can be
>    enabled automatically when the SR policy is applied.
> 
> 
> 
> 
> 
> 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.
> 
> The IETF Secretariat
> 
> 
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr