[Idr] 答复: 答复: [Lsr] New Version Notification for draft-wang-lsr-ospf-ifit-node-capability-02

wangyali <wangyali11@huawei.com> Mon, 16 March 2020 07:52 UTC

Return-Path: <wangyali11@huawei.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id B34353A20A3; Mon, 16 Mar 2020 00:52:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id pvubmziXqs5z; Mon, 16 Mar 2020 00:52:08 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com []) (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 148913A20A1; Mon, 16 Mar 2020 00:52:08 -0700 (PDT)
Received: from LHREML712-CAH.china.huawei.com (unknown []) by Forcepoint Email with ESMTP id 033671C27FC8B5D93BDB; Mon, 16 Mar 2020 07:52:06 +0000 (GMT)
Received: from DGGEML423-HUB.china.huawei.com ( by LHREML712-CAH.china.huawei.com ( with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 16 Mar 2020 07:52:05 +0000
Received: from DGGEML504-MBS.china.huawei.com ([]) by dggeml423-hub.china.huawei.com ([]) with mapi id 14.03.0487.000; Mon, 16 Mar 2020 15:51:58 +0800
From: wangyali <wangyali11@huawei.com>
To: "Acee Lindem (acee)" <acee@cisco.com>, "lsr@ietf.org" <lsr@ietf.org>
CC: IDR List <idr@ietf.org>
Thread-Topic: 答复: [Lsr] New Version Notification for draft-wang-lsr-ospf-ifit-node-capability-02
Thread-Index: AQHV+izlDugNgI5k20ScRLzeM0GA+qhK2GRQ
Date: Mon, 16 Mar 2020 07:51:57 +0000
Message-ID: <1520992FC97B944A9979C2FC1D7DB0F404DC657E@DGGEML504-MBS.china.huawei.com>
References: <C6D08B31-9B12-4EDA-9858-630E64D81270@cisco.com>
In-Reply-To: <C6D08B31-9B12-4EDA-9858-630E64D81270@cisco.com>
Accept-Language: en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/nHmpcJSs6Zgo2R8MSAwooak-VsU>
Subject: [Idr] 答复: 答复: [Lsr] New Version Notification for draft-wang-lsr-ospf-ifit-node-capability-02
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, 16 Mar 2020 07:52:10 -0000

Dear Acee,

Many thanks for your comments. Taking your suggestion I am writing a new LSR draft to combine the OSPF draft, ISIS draft and BGP-LS draft and will add more context on how to use the IFIT Capability information.

Best regards,

发件人: Acee Lindem (acee) [mailto:acee@cisco.com] 
发送时间: 2020年3月15日 2:18
收件人: wangyali <wangyali11@huawei.com>; lsr@ietf.org
抄送: IDR List <idr@ietf.org>
主题: Re: 答复: [Lsr] New Version Notification for draft-wang-lsr-ospf-ifit-node-capability-02

Hi Yali,
Please add some more context to the draft as to how the information will be used. I say draft rather than drafts since you can really combine the OSPF draft, IS-IS draft, and BGP-LS draft into a single LSR document. For RFC 8379, we included the BGP-LS specification in the OSPF draft and the IDR chairs have agreed to this for simple encodings such as this one.  

On 3/10/20, 4:46 AM, "wangyali" <wangyali11@huawei.com> wrote:

    Dear Acee,
    Thanks a lot for your comments. I have revised the title of drafts and will take your suggestion to add more text on how to use the IFIT Capability information, once the submission is opened. Here is my quick reply:
    IFIT is deployed in a specific domain referred as the IFIT domain. One network domain may consists of multiple IFIT domain. Within the IFIT domain, one or more IFIT-options are added into packet at the IFIT-enabled head node that is referred to as the “IFIT encapsulating node”. Then IFIT data fields MAY be updated by IFIT transit nodes that the packet traverses. Finally, the data fields are removed at a device that is referred to as the “IFIT decapsulating node”. 
    The IFIT data fields must not leak to other domains. So, the IFIT encapsulating node need to know if the decapsulating node is able to support the IFIT capability. So that it can decide whether to add the IFIT-option or not.
    The solution is similar to RFC8491. We use IGP to advertise the capability, so that head node can use. By using BGP-LS, a centralized controller can also learn the IFIT Capability of nodes to determine whether a particular IFIT Option type can be supported in a given network.
    Best regards,
    发件人: Acee Lindem (acee) [mailto:acee@cisco.com] 
    发送时间: 2020年3月9日 18:30
    收件人: wangyali <wangyali11@huawei.com>; lsr@ietf.org
    主题: Re: [Lsr] New Version Notification for draft-wang-lsr-ospf-ifit-node-capability-02
    Hi Yali,
    A couple of very basic comments on these drafts. They are definitely not ready for consideration. 
        1. IFIT is never expanded as an acronym. Seems it should be as early as the title. 
              OSPF extensions for Advertising In-Situ Flow Information Telemetry (IFIT) Capability
       2. You probably could come up with a more succinct acronym for IFIT. 
       3. The has no specification of how the capabilities are used. Are they purely informational? 
    On 3/9/20, 4:33 AM, "Lsr on behalf of wangyali" <lsr-bounces@ietf.org on behalf of wangyali11@huawei.com> wrote:
        Dear all,
        I'm Yali. Following is a new version of I-D, draft-wang-lsr-ospf-ifit-node-capability-02 I submitted recently.
        Please let me know your questions and comments. Thank you.
        Name:		draft-wang-lsr-ospf-ifit-node-capability
        Revision:	02
        Title:		Extensions to OSPF for Advertising IFIT Node Capability
        Document date:	2020-03-09
        Group:		Individual Submission
        Pages:		7
        URL:            https://www.ietf.org/internet-drafts/draft-wang-lsr-ospf-ifit-node-capability-02.txt
        Status:         https://datatracker.ietf.org/doc/draft-wang-lsr-ospf-ifit-node-capability/
        Htmlized:       https://tools.ietf.org/html/draft-wang-lsr-ospf-ifit-node-capability-02
        Htmlized:       https://datatracker.ietf.org/doc/html/draft-wang-lsr-ospf-ifit-node-capability
        Diff:           https://www.ietf.org/rfcdiff?url2=draft-wang-lsr-ospf-ifit-node-capability-02
           This document defines a way for an Open Shortest Path First (OSPF)
           router originating the RI LSA to announce IFIT node capabilities
           within the entire routing domain.  A new optional TLV is extended to
           the OSPF RI Opaque LSA [RFC7770] to carry the IFIT node capability
           information.  Such advertisements enable IFIT applications in an
           operational network domain.  Here, the term "OSPF" includes both
           OSPFv2 and OSPFv3.
        Best regards,
        Yali WANG
        Lsr mailing list