IETF Logo Mail Archive

Re: [OPSAWG] [Lsr] I,Scope of FIT Capability: a node or a link?

Jeff Tantsura <jefftant.ietf@gmail.com> Mon, 06 April 2020 18:32 UTC

Return-Path: <jefftant.ietf@gmail.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E7473A0C54; Mon, 6 Apr 2020 11:32:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 FfSewPwlazWS; Mon, 6 Apr 2020 11:32:52 -0700 (PDT)
Received: from mail-pj1-x1030.google.com (mail-pj1-x1030.google.com [IPv6:2607:f8b0:4864:20::1030]) (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 E6DA83A0C4F; Mon, 6 Apr 2020 11:32:51 -0700 (PDT)
Received: by mail-pj1-x1030.google.com with SMTP id k3so226406pjj.2; Mon, 06 Apr 2020 11:32:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:message-id:in-reply-to:references:subject :mime-version; bh=Q87xx3L/DZBCv1otZj8J1zLa0Z/DOWr90yIwzqvQBa8=; b=PDNT9mCSTAdWg0ZvodAmv3pNHCd0XIbhNazd9Mqeco+PCWu6vLz6magCHWV4llxdbb 4Wseu8l+OX3+Wl/V8d57/YV/u2AS6PasIpOyQE0hmA/pVwOhyUQXv1ddfwfFtlEXnFEQ q4kMtyzvA/fwoQrgnZ2glvd+dMOOgmd8RDL3qn/DpAqMGvb12sx/D6DXZ7RgKQNCDgo7 dMA7TyDUA7kLaJrg+ifFzu++FwIx9KvLDj+6is0lG2DY2NQsLlQgPGWaZxiSxI+Dz+U8 S6ZmOz89Bp2aqNjFQp+r5XrLp2NwxyjOBFvt66X5Ft7cZD5/+deTgW0IWPG+/567XcOg /DIg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:message-id:in-reply-to :references:subject:mime-version; bh=Q87xx3L/DZBCv1otZj8J1zLa0Z/DOWr90yIwzqvQBa8=; b=jAN1+pv9SWOXzj1xzJbWtN2V8ZfpE+xIGinlTzBCmTe6Z2mpO5IHmEW/IxkcScOwE7 BTNoYpFCpG0Ki7WrxeHJjxk/Z38sP2aI3IYBAolcATmzHDmI3A+VTmJUScK34bBU6T+p OxwB4XncJKCciAxDReo+b1fTd2NGFvJyFJLpuyd/bI9NLWMqHv5qIldLShAoOVDj278C xDFxHBy0IvFVC+44Pl/2C2YKJxiF9JsW9Bw0kkNYLK0H8oVeNWq0BcL3LQBP8InUe4jW nRgdN16r5KhNwc87klqprIhGB0kgUUdq+0SaNV81BkQI0khFwSRhGTvBwYbEmfPzk7aj 1fEg==
X-Gm-Message-State: AGi0PuZcFRm+pxIz+HfWiymk7T+zWrNXR7HCoNJfg6MxSwHRQ9IJM9oU 8D5CuSH/meCzAhCby3zCyZJO4hew
X-Google-Smtp-Source: APiQypKiA+d2BJqjy/rfbcnB8oV8nG73DC2txl3MIafW7MuxzU3Tvgdsn5tAayQbr2Kz762spIUV/A==
X-Received: by 2002:a17:90a:9e9:: with SMTP id 96mr746760pjo.168.1586197971113; Mon, 06 Apr 2020 11:32:51 -0700 (PDT)
Received: from [192.168.1.2] (c-73-63-232-212.hsd1.ca.comcast.net. [73.63.232.212]) by smtp.gmail.com with ESMTPSA id h26sm12080058pfr.134.2020.04.06.11.32.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 06 Apr 2020 11:32:50 -0700 (PDT)
Date: Mon, 06 Apr 2020 11:32:47 -0700
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: "Les Ginsberg (ginsberg)" <ginsberg=40cisco.com@dmarc.ietf.org>, Tony Li <tony1athome@gmail.com>
Cc: Greg Mirsky <gregimirsky@gmail.com>, "draft-song-opsawg-ifit-framework@ietf.org" <draft-song-opsawg-ifit-framework@ietf.org>, "lsr@ietf.org" <lsr@ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>, Tianran Zhou <zhoutianran@huawei.com>, "draft-wang-lsr-ifit-node-capability-advertisement@ietf.org" <draft-wang-lsr-ifit-node-capability-advertisement@ietf.org>
Message-ID: <881907b7-420a-4fe2-bb71-722d1f50daf8@Spark>
In-Reply-To: <BFBEF91A-7FD0-494D-A69F-0F9319EAD2C7@gmail.com>
References: <4da3d82b084343bfa18de192b1f390b1@huawei.com> <MW3PR11MB4619DBDBD80BC52A92F51176C1C20@MW3PR11MB4619.namprd11.prod.outlook.com> <BFBEF91A-7FD0-494D-A69F-0F9319EAD2C7@gmail.com>
X-Readdle-Message-ID: 881907b7-420a-4fe2-bb71-722d1f50daf8@Spark
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="5e8b75cf_62b83e2b_16f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/5K1g-pQKc80c8zuBCVws2McRRt4>
Subject: Re: [OPSAWG] [Lsr] I,Scope of FIT Capability: a node or a link?
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Apr 2020 18:32:54 -0000

+1
Please do not take my comments about link vs node capabilities, as support for the solution, they are semantical.

Cheers,
Jeff
On Apr 6, 2020, 8:58 AM -0700, Tony Li <tony1athome@gmail.com>, 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.
>
>
> +1
>
> IS-IS is not the correct place to implement Service Discovery mechanisms. The management plane already has ample mechanisms for service and capability discovery.
>
> Tony
>
>
> _______________________________________________
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr

v2.23.0 | Report a Bug | By Email