[Lsr] 答复: New Version Notification for draft-wang-lsr-igp-extensions-ifit-00.txt

qinfengwei <qinfengwei@chinamobile.com> Mon, 20 July 2020 01:31 UTC

Return-Path: <qinfengwei@chinamobile.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1556D3A0BEA for <lsr@ietfa.amsl.com>; Sun, 19 Jul 2020 18:31:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=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 OYokm_wlOL1j for <lsr@ietfa.amsl.com>; Sun, 19 Jul 2020 18:31:12 -0700 (PDT)
Received: from cmccmta3.chinamobile.com (cmccmta3.chinamobile.com [221.176.66.81]) by ietfa.amsl.com (Postfix) with ESMTP id 9D5FD3A0CB4 for <lsr@ietf.org>; Sun, 19 Jul 2020 18:31:09 -0700 (PDT)
Received: from spf.mail.chinamobile.com (unknown[172.16.121.9]) by rmmx-syy-dmz-app12-12012 (RichMail) with SMTP id 2eec5f14f3c49e3-56d11; Mon, 20 Jul 2020 09:30:45 +0800 (CST)
X-RM-TRANSID: 2eec5f14f3c49e3-56d11
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from cmccPC (unknown[117.136.38.146]) by rmsmtp-syy-appsvr05-12005 (RichMail) with SMTP id 2ee55f14f3c3672-020ce; Mon, 20 Jul 2020 09:30:44 +0800 (CST)
X-RM-TRANSID: 2ee55f14f3c3672-020ce
From: qinfengwei <qinfengwei@chinamobile.com>
To: 'wangyali' <wangyali11@huawei.com>, lsr@ietf.org
References: <159464612771.23915.16999479503429391526@ietfa.amsl.com> <1520992FC97B944A9979C2FC1D7DB0F404F012B8@dggeml524-mbx.china.huawei.com>
In-Reply-To: <1520992FC97B944A9979C2FC1D7DB0F404F012B8@dggeml524-mbx.china.huawei.com>
Date: Mon, 20 Jul 2020 09:30:42 +0800
Message-ID: <010601d65e35$63018550$29048ff0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AQHWWRe0fdnLGyv4nU2MCh5oJ0Wq7akKRYeQgAVy5DA=
Content-Language: zh-cn
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/7Is8oEqnA7uKRUQ2omW2fQu92Yw>
Subject: [Lsr] 答复: New Version Notification for draft-wang-lsr-igp-extensions-ifit-00.txt
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jul 2020 01:31:17 -0000

Hi,
	IFIT Capability Advertisement accurately tracks the urgent requirements and real challenges when IFIT implementation.
	Right now, the IFIT test has been performed and is under implementation. We found that signaling Node IFIT capability to ingress nodes is indeed helpful for determining whether IFIT header and data fields could be encapsulated in packets.



Thanks,
Fengwei Qin

-----邮件原件-----
发件人: wangyali [mailto:wangyali11@huawei.com] 
发送时间: 2020年7月16日 23:20
收件人: 'lsr@ietf.org'
主题: FW: New Version Notification for draft-wang-lsr-igp-extensions-ifit-00.txt

Dear LSR WG,

We've uploaded a new revision of draft-wang-lsr-igp-extensions-ifit-00 to replace draft-wang-lsr-ifit-node-capability-advertisement. In this new revision, Node and Link Attribute TLVs are extended to IGP for signaling the supported IFIT capability of egress and/or intermediate nodes to the ingress nodes.

The changes in this revision are:

1. added Link Attribute TLVs extension to IGP to signal IFIT Capability at link granularity.
2. updated Application section, which illustrates such advertisements would helpful for avoiding the leak of IFIT-specific header and metadata, as well as, for ingress routers to gather each router's IFIT capability for achieving the computation of TE paths or loose TE paths that be able to fulfill the visibility of on-path OAM data.
3. updated Acknowledgements sections, in which, the authors would like to thank Acee Lindem, Christian Hopps, Robert Raszuk, Les Ginsberg, Jeff Tantsura, Rakesh Gandhi, Tony Li and Greg Mirsky for the comments.
4. adding China Telecom into the author list.

We are looking forward to hearing your feedback and comments, and try to achieve consensus.

Thanks,
Yali


-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
Sent: Monday, July 13, 2020 9:15 PM
To: Tianran Zhou <zhoutianran@huawei.com>; wangyali <wangyali11@huawei.com>; Huanan Chen <chenhuan6@chinatelecom.cn>; Liumin (Lucy) <lucy.liumin@huawei.com>; Ran Pang <pangran@chinaunicom.cn>; Liumin (Lucy) <lucy.liumin@huawei.com>
Subject: New Version Notification for draft-wang-lsr-igp-extensions-ifit-00.txt


A new version of I-D, draft-wang-lsr-igp-extensions-ifit-00.txt
has been successfully submitted by Yali Wang and posted to the IETF repository.

Name:           draft-wang-lsr-igp-extensions-ifit
Revision:       00
Title:          IGP Extensions for In-situ Flow Information Telemetry (IFIT) Capability Advertisement
Document date:  2020-07-12
Group:          Individual Submission
Pages:          12
URL:            https://www.ietf.org/internet-drafts/draft-wang-lsr-igp-extensions-ifit-00.txt
Status:         https://datatracker.ietf.org/doc/draft-wang-lsr-igp-extensions-ifit/
Htmlized:       https://tools.ietf.org/html/draft-wang-lsr-igp-extensions-ifit-00
Htmlized:       https://datatracker.ietf.org/doc/html/draft-wang-lsr-igp-extensions-ifit


Abstract:
   This document extends Node and Link Attribute TLVs to Interior
   Gateway Protocols (IGP) to advertise supported In-situ Flow
   Information Telemetry (IFIT) capabilities at node and/or link
   granularity.  An ingress router cannot insert IFIT-Data-Fields for
   packets going into a path unless an egress router has indicated via
   signaling that it has the capability to process IFIT-Data-Fields.  In
   addition, such advertisements would be useful for ingress routers to
   gather each router's IFIT capability for achieving the computation of
   Traffic Engineering (TE) paths or loose TE paths that be able to
   fulfill the visibility of on-path OAM data.





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