From nobody Wed Sep 30 01:07:29 2020 Return-Path: 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 BB2483A12C9; Wed, 30 Sep 2020 01:07:28 -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 mryr7cjtO-aq; Wed, 30 Sep 2020 01:07:26 -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 66FA33A12C8; Wed, 30 Sep 2020 01:07:26 -0700 (PDT) Received: from lhreml724-chm.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 1D6F3D815F86FFDAF661; Wed, 30 Sep 2020 09:07:25 +0100 (IST) Received: from fraeml712-chm.china.huawei.com (10.206.15.61) by lhreml724-chm.china.huawei.com (10.201.108.75) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Wed, 30 Sep 2020 09:07:24 +0100 Received: from dggeme754-chm.china.huawei.com (10.3.19.100) by fraeml712-chm.china.huawei.com (10.206.15.61) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.1913.5; Wed, 30 Sep 2020 10:07:23 +0200 Received: from dggeme754-chm.china.huawei.com ([10.6.80.77]) by dggeme754-chm.china.huawei.com ([10.6.80.77]) with mapi id 15.01.1913.007; Wed, 30 Sep 2020 16:07:21 +0800 From: "Dongjie (Jimmy)" To: Giuseppe Fioccola , "idr@ietf.org" CC: "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+4kwgCd6FaCAAYjncIABiUww Date: Wed, 30 Sep 2020 08:07:21 +0000 Message-ID: <619adfba678442e4aff0e362c0d7403d@huawei.com> References: <159903280992.25091.5278946449904193569@ietfa.amsl.com> <55226955c0a3414d842e7b33e9fb9c35@huawei.com> In-Reply-To: Accept-Language: en-US, zh-CN Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.108.243.143] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-CFilter-Loop: Reflected Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Sep 2020 08:07:29 -0000 Hi Giuseppe, Thanks for your reply.=20 The changes in plan looks good to me. Look forward to a updated version. Best regards, Jie > -----Original Message----- > From: Giuseppe Fioccola > Sent: Monday, September 28, 2020 6:38 PM > To: Dongjie (Jimmy) ; 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 >=20 > Hi Jie, > Thanks a lot for your review. > Please find my answers inline tagged as [GF]. >=20 > Regards, >=20 > Giuseppe >=20 > -----Original Message----- > From: Dongjie (Jimmy) > Sent: Sunday, September 27, 2020 12:53 PM > To: Giuseppe Fioccola ; 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 >=20 > Hi Giuseppe, >=20 > Thanks for this update, here are some review comments from my side: >=20 > 1. This document defines several sub-TLVs under BGP Tunnel Encapsulation > Attribute for different IFIT related functions. Perhaps it would be bette= r to > define just one sub-TLV for IFIT, then define the different IFIT function= s 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. >=20 > 2. In addition to describing the encoding of the sub-TLVs, it may be help= ful to > also describe the operation of node when receiving an SR policy with thes= e 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 additi= on of > IFITAttributes Sub-TLVs is handled for the SR Policy NLRI. >=20 > Best regards, > Jie >=20 > > -----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 ; Fengwei Qin > > ; wangyali ; > Hang > > Yuan ; Tianran Zhou > > 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.tx= t > > Status: https://datatracker.ietf.org/doc/draft-qin-idr-sr-polic= y-ifit/ > > Htmlized: https://tools.ietf.org/html/draft-qin-idr-sr-policy-ifi= t-03 > > Htmlized: > > https://datatracker.ietf.org/doc/html/draft-qin-idr-sr-policy-ifit > > Diff: > https://www.ietf.org/rfcdiff?url2=3Ddraft-qin-idr-sr-policy-ifit-03 > > > > Abstract: > > Segment Routing (SR) policy is a set of candidate SR paths consistin= g > > 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.i= etf.org. > > > > The IETF Secretariat > > > > > > _______________________________________________ > > Idr mailing list > > Idr@ietf.org > > https://www.ietf.org/mailman/listinfo/idr