Re: [Lsr] I,Scope of FIT Capability: a node or a link?
Tony Przygienda <tonysietf@gmail.com> Mon, 06 April 2020 18:56 UTC
Return-Path: <tonysietf@gmail.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 9CCB73A07A0; Mon, 6 Apr 2020 11:56:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.938
X-Spam-Level:
X-Spam-Status: No, score=-1.938 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, THIS_AD=0.148, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 pMQ366P-hCUB; Mon, 6 Apr 2020 11:56:38 -0700 (PDT)
Received: from mail-il1-x12d.google.com (mail-il1-x12d.google.com [IPv6:2607:f8b0:4864:20::12d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 645AA3A040A; Mon, 6 Apr 2020 11:56:38 -0700 (PDT)
Received: by mail-il1-x12d.google.com with SMTP id n13so561683ilm.5; Mon, 06 Apr 2020 11:56:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=aZxuP64gqfD+XpIiv/V4OCrScq4kbBxFD4hSV8wEDBw=; b=lv/D8tnEmNRwRD867E7arj90+l7Rr/063X9TP0tjQaPBtViz+VGDlSZMLkrxeKnsHV JHU9U9Cx6P1wTxKQYWrhG9zCVq0/vJEoHJ4haI4Y0wdDOeeHP8GFQ5aoMfut/d/M3oIc eDgKUCXh7Rx7eARgZWpzYyBNGxMxHNTwtcw3+Ra7bTnam0AXccJ1r+oiubfh68cr/zAu Vi9UjTl1LeJSmE7wStmrgIpcPvoDHn4JhP9UVZjgpMpE8XJ9JoiY535d03I/ZmQpF0c9 1ZMHqZ29henERPGp59j4v56PA8nbDs4JXSZBc6dRhIoccU2321qVB5sRi9Qj1LkSrU+d YCbw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=aZxuP64gqfD+XpIiv/V4OCrScq4kbBxFD4hSV8wEDBw=; b=uZFxOK4F9qyeFQ5xLlDmIjFUYlmpa+m9SiJwA6bn6zZY4IsauSRAqW4CprKYpG52OQ rIlSXmzbYJFmpVOdOh7dJW4rpPGxC00Vj75rk7lDIFOTe3NzYsT+i+I++RD6Emw4JaP4 oocKydehk3i5d7zPIiiUIKto5bZ3RvDQupZcuBQ5V5FDvu9OceyQ8Ci6bqtPnuAI8Ivf AySR3bzW3oLbZ1Sn93QTwcTgQbYUmmfCfeKIvLV9OXXYD5omj2YpnAaYVjj4Fj9eUBaY jH/9znIguMqqq0GZoBKyg+sNqFiui55f6Flx9bkhRlNRzISan2C3iX+11/2M2qm8VtHR ZYHw==
X-Gm-Message-State: AGi0PuZoZ3PXt7o16sZlUzTxQh3QYzHYs+2TxVBxT7B5hTGcb8I2WusJ KYECBomipSQtdETf6OYbMHjDv5OXHlGeIibX54s=
X-Google-Smtp-Source: APiQypJoRDlc4f48LB5t7RSk5sZAU35SsrM2PpnAonnU6NLbrGEthFXa3d7N9FiVOWPgdyUZO1xYB36Wn782tbAkyjk=
X-Received: by 2002:a92:5e91:: with SMTP id f17mr796672ilg.239.1586199397603; Mon, 06 Apr 2020 11:56:37 -0700 (PDT)
MIME-Version: 1.0
References: <4da3d82b084343bfa18de192b1f390b1@huawei.com> <MW3PR11MB4619DBDBD80BC52A92F51176C1C20@MW3PR11MB4619.namprd11.prod.outlook.com>
In-Reply-To: <MW3PR11MB4619DBDBD80BC52A92F51176C1C20@MW3PR11MB4619.namprd11.prod.outlook.com>
From: Tony Przygienda <tonysietf@gmail.com>
Date: Mon, 06 Apr 2020 11:55:55 -0700
Message-ID: <CA+wi2hOZOncTqo9XBSfiMoE5OKp5WfHaXAmANv_cXLFtn_deLw@mail.gmail.com>
To: "Les Ginsberg (ginsberg)" <ginsberg=40cisco.com@dmarc.ietf.org>
Cc: Tianran Zhou <zhoutianran@huawei.com>, Greg Mirsky <gregimirsky@gmail.com>, "draft-wang-lsr-ifit-node-capability-advertisement@ietf.org" <draft-wang-lsr-ifit-node-capability-advertisement@ietf.org>, "lsr@ietf.org" <lsr@ietf.org>, "draft-song-opsawg-ifit-framework@ietf.org" <draft-song-opsawg-ifit-framework@ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a3224d05a2a3d324"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/94Lr35Af6SbO3MoMHMBDgoogNIY>
Subject: Re: [Lsr] I,Scope of FIT Capability: a node or a link?
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, 06 Apr 2020 18:56:48 -0000
+1 IGP is NOT an AD scope generic L3 broadcast mechanism ;-) BGP is NOT an world scope generic L3 broadcast mechanism ;-) --- tony On Mon, Apr 6, 2020 at 8:06 AM Les Ginsberg (ginsberg) <ginsberg= 40cisco.com@dmarc.ietf.org> wrote: > This discussion is interesting, but please do not ignore the considerable > feedback from multiple folks indicating that this advertisement does not > belong in the IGP at all (regardless of scope). > > My opinion on that has not changed. > > > > Thanx. > > > > Les > > > > > > > > *From:* Lsr <lsr-bounces@ietf.org> *On Behalf Of *Tianran Zhou > *Sent:* Monday, April 06, 2020 7:48 AM > *To:* Greg Mirsky <gregimirsky@gmail.com>; > draft-wang-lsr-ifit-node-capability-advertisement@ietf.org; lsr@ietf.org; > draft-song-opsawg-ifit-framework@ietf.org; opsawg@ietf.org > *Subject:* Re: [Lsr] I,Scope of FIT Capability: a node or a link? > > > > Hi Greg, > > > > Thanks very much for your interest on both IFIT framework and IFIT > capability draft. And thanks for your review comments. > > Your perspective on both drafts are correct. > > On the node or link capability, thanks for your suggestion. > > I agree with both you and Jeff. The link capability can make the > information more clear and accurate for different scenarios. > > Why we only considered the node capability? That’s the trade off to reduce > complexity. We just want to start from simple cases. > > If the WG think link capability is necessary, we would like to add link > capabilities to the update. > > > > Cheers, > > Tianran > > > > *发件人**:* Greg Mirsky [mailto:gregimirsky@gmail.com <gregimirsky@gmail.com>] > > *发送时间:* 2020年4月5日 10:33 > *收件人:* draft-wang-lsr-ifit-node-capability-advertisement@ietf.org; > lsr@ietf.org; draft-song-opsawg-ifit-framework@ietf.org; opsawg@ietf.org > *主题:* I,Scope of FIT Capability: a node or a link? > > > > Dear All, > > I've read these two drafts with interest. In light of the discussion on > the LSR WG list, I've been thinking about the scenarios where IFIT is being > used. > > draft-song-opsawg-ifit-framework defines the overall IFIT architecture > that, as I understand it, applicable to different methods of collecting and > transporting telemetry > information. draft-wang-lsr-ifit-node-capability-advertisement is based on > the view that IFIT is a node-wide capability advertised as a binary flag > for each listed method of collecting telemetry information (Option-Type > enabled Flag). On-path telemetry collection is performed in the fast path, > i.e., at a link layer. But a node might include ports with different > capabilities. How such a heterogeneous, IFIT-wise, node will advertise IFIT > Capability? To better use available resources for telemetry information > collection, it might be helpful to advertise IFIT as a capability of a > link, not of a node? > > What do you think? > > > > Regards, > > Greg > _______________________________________________ > Lsr mailing list > Lsr@ietf.org > https://www.ietf.org/mailman/listinfo/lsr >
- [Lsr] I,Scope of FIT Capability: a node or a link? Greg Mirsky
- Re: [Lsr] I,Scope of FIT Capability: a node or a … Jeff Tantsura
- Re: [Lsr] I,Scope of FIT Capability: a node or a … Tianran Zhou
- Re: [Lsr] I,Scope of FIT Capability: a node or a … Les Ginsberg (ginsberg)
- Re: [Lsr] I,Scope of FIT Capability: a node or a … Tony Li
- Re: [Lsr] I,Scope of FIT Capability: a node or a … Jeff Tantsura
- Re: [Lsr] I,Scope of FIT Capability: a node or a … Acee Lindem (acee)
- Re: [Lsr] I,Scope of FIT Capability: a node or a … Tony Przygienda
- Re: [Lsr] I,Scope of FIT Capability: a node or a … Tianran Zhou
- Re: [Lsr] I,Scope of FIT Capability: a node or a … Acee Lindem (acee)
- Re: [Lsr] I,Scope of FIT Capability: a node or a … Acee Lindem (acee)
- Re: [Lsr] I,Scope of FIT Capability: a node or a … Tianran Zhou
- Re: [Lsr] I,Scope of FIT Capability: a node or a … Tianran Zhou
- Re: [Lsr] I,Scope of FIT Capability: a node or a … Acee Lindem (acee)
- Re: [Lsr] I,Scope of FIT Capability: a node or a … Tianran Zhou