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

"Acee Lindem (acee)" <acee@cisco.com> Sun, 29 March 2020 17:15 UTC

Return-Path: <acee@cisco.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 79E463A0F66; Sun, 29 Mar 2020 10:15:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.7
X-Spam-Level:
X-Spam-Status: No, score=-7.7 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=g8/1sfN7; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=ZOUAE7d3
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 t8G3vUxSc0_e; Sun, 29 Mar 2020 10:15:37 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2929B3A0F65; Sun, 29 Mar 2020 10:15:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8330; q=dns/txt; s=iport; t=1585502137; x=1586711737; h=from:to:cc:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=KZMlLQeEg7+f/Lmzq1kgoSJ2PWdPz9Lgp4lYxuiuYMY=; b=g8/1sfN7WEzFadgAjzvyRXt1wT9lTaRwJcnPdil+hTbbB5YherADkBcT 4nW8iqReMIItNva230+WEZlvt4P7Hwpjg9Tcf8ZydImGBt3ydC7Eg5xz2 X3Y2auMqFMX0QBOsE/dZrHKX3tZqmC9L7gypw3sO8SZ5obQA8O+ChNXPU A=;
IronPort-PHdr: =?us-ascii?q?9a23=3APHyblxWKtauMRUJPL0nkrG0iJm/V8LGuZFwc94?= =?us-ascii?q?YnhrRSc6+q45XlOgnF6O5wiEPSANiJ8OpK3uzRta2oGXcN55qMqjgjSNRNTF?= =?us-ascii?q?dEwd4TgxRmBceEDUPhK/u/Zic3EexJVURu+DewNk0GUMs=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CbBQB514Be/4MNJK1mHAEBAQEBBwE?= =?us-ascii?q?BEQEEBAEBgXuBVCknBWxYIAQLKgqEEINFA4prmn6BQoEQA1QKAQEBDAEBGA0?= =?us-ascii?q?IAgQBAYREGYIaJDgTAgMBAQsBAQUBAQECAQUEbYVWDIVxAgEDAQEQEREMAQE?= =?us-ascii?q?sCQIBEQEGAhoCIwMCBCULFAEFDQQBDQUbB4MEAYJLAy4BDo9+kGcCgTmIYnW?= =?us-ascii?q?BMoJ/AQEFgTMCDkGDNBiCDAMGgQ4qjDEaggCBEAEnIIJNPoJnAQECAQEYgQ8?= =?us-ascii?q?ggywygiyQeoYemVEKgjyHYYgKhyodgkyIMAWQa4NUi0WJFpJtAgQCBAUCDgE?= =?us-ascii?q?BBYFpIoFYcBUaISoBgkFQGA2OHTgbVAEIgkOFFIVBdAKBJ4xBAYEPAQE?=
X-IronPort-AV: E=Sophos;i="5.72,321,1580774400"; d="scan'208";a="454866498"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 29 Mar 2020 17:15:34 +0000
Received: from XCH-ALN-001.cisco.com (xch-aln-001.cisco.com [173.36.7.11]) by alln-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id 02THFXQR027393 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Sun, 29 Mar 2020 17:15:33 GMT
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by XCH-ALN-001.cisco.com (173.36.7.11) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Sun, 29 Mar 2020 12:15:33 -0500
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Sun, 29 Mar 2020 12:15:32 -0500
Received: from NAM10-BN7-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Sun, 29 Mar 2020 13:15:32 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ViQf2Qjnq8pOhBYXO4/dZxXKNvKpriipuKGVC2dLquxcBO1xwWaH1OpQdW+OPIe0hDidderIPOU9cXW43uldvilgNmSR/+bvJAw8SOTpy7JtUta3OgIHzE/nHIYiZiAvBoO52Aqdl2W3/MiRS62LNu72Pkn6XJrytOUj4GsUS4Os4nMP1pgXytjnA4G+72aVK1XBFExm5wbT8z/4jF3clI8/RZ5l5JDnfCiHGQgo5WoKg8ZPxf+fH2lwTlNDpnjQ2KWHZ/ogOiRL4CpBdUZIK5hZ/Awh3vGT7F3ipSLlgn2krqgJH31U4zzfCedoDOeSRN0NYFVB3qcEcfGiuYZgBw==
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=KZMlLQeEg7+f/Lmzq1kgoSJ2PWdPz9Lgp4lYxuiuYMY=; b=nUl77TA5p+rITz5/SFqQMtF/mn7+MYhqSZzA48YD+S6GjZfMskxUiAQTRfu/3zaSHXkYpfx31hvXvU720oEUOFzl8WB8zR15c23WMHuH6qCIv+MXexXCCQ7MxpumO5dHItN9XLUdMhcINJPaYIE9wGUf/j/G/HTTk/2C8oEmcHr8wO0ealhyhU5gL+N0WR4RmNgWU1YBezjNROrQWNoOmszP8uRMznguGuCdP4YacQNkkW5IP5q0z38g1814mOzzHaWAJsxGgboDt9y7h2C8YeapkgvCiZx6C4EsgPryY73cDaNdnvhKw83iAoGJetc+qXX2FixCkVSW4GZwP9xuXQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=KZMlLQeEg7+f/Lmzq1kgoSJ2PWdPz9Lgp4lYxuiuYMY=; b=ZOUAE7d3fY6hzzdzcq82jwCzBWoKorBCdFFwoLi0z4bgKFpy86Iq3dEIQ9iyt3Mh/W1/IDvFYHF1mV8lUXIdLh5ruWBxTFmmYSZC2vi2q4U9CemAg9sj70Fg31dJxG819OmKJm8pVzAUHYngc4chfPzY54KCiOmcGEULnkBxtYs=
Received: from BN8PR11MB3794.namprd11.prod.outlook.com (2603:10b6:408:8f::13) by BN8PR11MB3793.namprd11.prod.outlook.com (2603:10b6:408:86::23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2856.20; Sun, 29 Mar 2020 17:15:32 +0000
Received: from BN8PR11MB3794.namprd11.prod.outlook.com ([fe80::55b2:c415:675f:5fb7]) by BN8PR11MB3794.namprd11.prod.outlook.com ([fe80::55b2:c415:675f:5fb7%3]) with mapi id 15.20.2856.019; Sun, 29 Mar 2020 17:15:31 +0000
From: "Acee Lindem (acee)" <acee@cisco.com>
To: wangyali <wangyali11@huawei.com>, "lsr@ietf.org" <lsr@ietf.org>
CC: IDR List <idr@ietf.org>
Thread-Topic: =?utf-8?B?562U5aSNOiAg562U5aSNOiBbTHNyXSBOZXcgVmVyc2lvbiBOb3RpZmljYXRp?= =?utf-8?B?b24gZm9yIGRyYWZ0LXdhbmctbHNyLW9zcGYtaWZpdC1ub2RlLWNhcGFiaWxp?= =?utf-8?Q?ty-02?=
Thread-Index: AQHWBe2mrCEJ/rITrkOAt0qMSUkkig==
Date: Sun, 29 Mar 2020 17:15:31 +0000
Message-ID: <36D8F62A-FABA-48BD-BAFB-13EC6C494A65@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.35.20030802
authentication-results: spf=none (sender IP is ) smtp.mailfrom=acee@cisco.com;
x-originating-ip: [136.56.133.70]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 1047e197-b00b-4a4d-723a-08d7d404c95b
x-ms-traffictypediagnostic: BN8PR11MB3793:
x-microsoft-antispam-prvs: <BN8PR11MB37930C0DEA6634A6EDCC4F72C2CA0@BN8PR11MB3793.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 035748864E
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BN8PR11MB3794.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(10009020)(4636009)(136003)(366004)(396003)(346002)(376002)(39860400002)(53546011)(110136005)(6506007)(5660300002)(33656002)(6486002)(2616005)(36756003)(2906002)(6512007)(64756008)(186003)(8936002)(224303003)(15650500001)(86362001)(81156014)(81166006)(71200400001)(478600001)(4326008)(26005)(76116006)(66476007)(316002)(66946007)(66446008)(91956017)(966005)(66556008)(66574012); DIR:OUT; SFP:1101;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: uCKw1X+zCJH/a10hfZT916hD7KtcbeHpj9CX+doiM2P2bc6e6cP47u9JpJG72P+own4K8KJYm1NzqUDsCHuGxbv5KSo9DhKFpmJpygtUCE+k5gkdc4hFj5RnpgGWQuaN3FBQtBiILfYJdx++KWmE17jWxIvWCNsZLuqHiy1xeGLvsgmu8u+3JzjLNBivTYuon/O4xQrfxFSK8k+9ayW72z0W4b0bKzl5PKv6yrxswj5xOoHGIwljFxZVTMmtyXrOlp4Cwp7omxd8upOl9LDEz69lhzRZJkJCPScNPYpw9JiWJ8YI7byqylI6caKnH7hu5WxFhgM85cmUjzYYfrK1Xh3eGSMm4tHNuOu2CC1mY48dWm1jz8YXGuG6NrwGRyFrwYhX3mIykyVQiWawZIoYzOPxjpMDOnff32+cx+rpX+vKdD3I8fxfwWH+a8BWFGnOFO/mZuJK33jS7Xez3lGYaG3mNyT+hbl4j3SwlrCiIHgzEsvcXSOwewfXOD3jDUujlhApyX8CeDHg/YUirSnGTw==
x-ms-exchange-antispam-messagedata: KsEhRNRPY79Af7jqxnHdg6+LcTG+Qn+O6SBiQc7QD/Z4303DSHD3vPwfbgN2onWBSIgjTOqlAFSs77f77472d0ZV7M3EF4Zenc54jr+KSnvGEh5UScrLNoOxOO3eBtQlGy5XNUFKL6eqoUpp6DIoDw==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <7317D482C11D92418524219B50D9190B@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 1047e197-b00b-4a4d-723a-08d7d404c95b
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Mar 2020 17:15:31.7486 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: meI04t7UPr/4khkbQza8psZGIt8/l3qoAo7HEVODXNZdJB1Pmxau7zkFJJwz1dsQ
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN8PR11MB3793
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.11, xch-aln-001.cisco.com
X-Outbound-Node: alln-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/eVVgeDdPCESpnmqNCTOFpNqxaYw>
Subject: Re: [Idr] =?utf-8?b?562U5aSNOiAg562U5aSNOiBbTHNyXSBOZXcgVmVyc2lvbiBO?= =?utf-8?q?otification_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: Sun, 29 Mar 2020 17:15:40 -0000

Hi Yali, 

Thanks for the quick turn around with the version incorporating my comments. 

https://datatracker.ietf.org/doc/draft-wang-lsr-ifit-node-capability-advertisement/

This is the organization of draft that I had in mind. It may need some more references to https://datatracker.ietf.org/doc/draft-song-opsawg-ifit-framework/ but that can come if the work progresses in OPSAWG.  Also, I was surprised not to see more discussion of the identifiers and name spaces in the base framework document. 

Thanks,
Acee 

On 3/16/20, 3:52 AM, "wangyali" <wangyali11@huawei.com> wrote:

    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,
    Yali
    
    -----邮件原件-----
    发件人: Acee Lindem (acee) [mailto:acee@cisco.com] 
    发送时间: 2020年3月15日 2:18
    收件人: wangyali <wangyali11@huawei.com>om>; 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.  
    Thanks,
    Acee
    
    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,
        Yali
        
        -----邮件原件-----
        发件人: Acee Lindem (acee) [mailto:acee@cisco.com] 
        发送时间: 2020年3月9日 18:30
        收件人: wangyali <wangyali11@huawei.com>om>; 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? 
        
        Thanks,
        Acee
        
         
        
        
        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
            
            Abstract:
               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
            Lsr@ietf.org
            https://www.ietf.org/mailman/listinfo/lsr