[Lsr] Considerations for Extended TE Metrics (draft-ietf-isis-te-app)
Alvaro Retana <aretana.ietf@gmail.com> Thu, 14 May 2020 17:27 UTC
Return-Path: <aretana.ietf@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 E41933A0C18; Thu, 14 May 2020 10:27:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 8RIrZ7I51ghD; Thu, 14 May 2020 10:27:04 -0700 (PDT)
Received: from mail-wr1-x429.google.com (mail-wr1-x429.google.com [IPv6:2a00:1450:4864:20::429]) (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 795223A0C59; Thu, 14 May 2020 10:27:00 -0700 (PDT)
Received: by mail-wr1-x429.google.com with SMTP id i15so5280405wrx.10; Thu, 14 May 2020 10:27:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:mime-version:date:message-id:subject:to:cc :content-transfer-encoding; bh=b6eT0QbKK4Bq38oUFR3YHWj6dPRHkDluAApG+xKad6M=; b=FyilZWyBIOZcd7v2+mFQeG1wUZSKEO8weKuWK3CSWewMS64FXCiS446nhzdWVJ8h6T rQ6ESyzOkUYphKIbXMrk4KXOH4usm6QzjOK/QZnaMmpTIA01rxl+BcguzVWjuEVpYFZ7 icfVLwASO/UAKQF7+R0MaHtb6iaKTtS688hFblZ4dMeUUBbz5JxfGqTBOrrsRW2thV/0 4PCgqiRllhRc0QE8OZTfuNBuSgPrfYw/OOVAqQ1OYC2yTXPEgkhtHPYDTkwBeKICbRsP 21lNcnnzfpoy9lcsnXgWXtBjKRYu8QeiXYIIRsGAoFJ0KcyVe4QLCLPE9SvHLuBEnDmz 8oGQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:date:message-id:subject:to:cc :content-transfer-encoding; bh=b6eT0QbKK4Bq38oUFR3YHWj6dPRHkDluAApG+xKad6M=; b=JfV+uGoaO7X30UqGwOyPMYwESXr46U+EyFgKQJOorz1SxOjoM13kFoUZKYU8KgSV5t 4gx++MbGYLL8IOnrjiUL1/q4PIHXQw1bohEYeHqtEnN6g4lP+2qWEGe+CIyaM2+Ro/mW DI1MN4nvlG+jEtm51H/AZYE9s+nB56BAfZ2uV55r+z8fNLT61vCtZrtJsOE4HAc0rPPL UkdzNeDY9OisPAB9VkYAVpsRBTq24MtvycUfrGCNt/XQPZsLLKRxV5gzgYbpB9kJuqvM oKczq75U8w7D6MDpRAtt95xCPC7gTzZY2ENEUXSsqzdayqTXyLW1OclMu9HvdblqmEr3 fHnw==
X-Gm-Message-State: AOAM533iWCnC+P3st5Ge1cSrA+knXdRIhVWMNDm0upNt7jYl8YdRrDp4 Ki/qj08BifMevMV20AbyTO8xEWDRxNQRAqPO6NmtUsj/
X-Google-Smtp-Source: ABdhPJympnl8C1hgFbMAud7uHtblslwwbjYD8MYUC899HBnTH+OLcxhe+IszRA61kcoE/oM5Ndxgu5bBPUcegezCNZ4=
X-Received: by 2002:a5d:6943:: with SMTP id r3mr4721710wrw.113.1589477218376; Thu, 14 May 2020 10:26:58 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Thu, 14 May 2020 10:26:57 -0700
From: Alvaro Retana <aretana.ietf@gmail.com>
MIME-Version: 1.0
Date: Thu, 14 May 2020 10:26:57 -0700
Message-ID: <CAMMESswi7Jtxe32pRY7ZwF5WFGBk50g-LrYhXt_D5A0p9joc9g@mail.gmail.com>
To: draft-ietf-isis-te-app.authors@ietf.org
Cc: draft-ietf-ospf-te-link-attr-reuse@ietf.org, "lsr-chairs@ietf.org" <lsr-chairs@ietf.org>, lsr@ietf.org, Yingzhen Qu <yingzhen.qu@futurewei.com>, "Acee Lindem (acee)" <acee@cisco.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/Xyq9HVe0KR0qrF4i2sXhXq-32AY>
Subject: [Lsr] Considerations for Extended TE Metrics (draft-ietf-isis-te-app)
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: Thu, 14 May 2020 17:27:09 -0000
Dear authors: When reviewing the updates to draft-ietf-ospf-te-link-attr-reuse-11, I noticed the following difference with respect to draft-ietf-isis-te-app-12: [] draft-ietf-isis-te-app-12: 437 4.2.3. Considerations for Extended TE Metrics 439 [RFC8570] defines a number of dynamic performance metrics associated 440 with a link. It is conceivable that such metrics could be measured 441 specific to traffic associated with a specific application. 442 Therefore this document includes support for advertising these link 443 attributes specific to a given application. However, in practice it 444 may well be more practical to have these metrics reflect the 445 performance of all traffic on the link regardless of application. In 446 such cases, advertisements for these attributes will be associated 447 with all of the applications utilizing that link. [] draft-ietf-ospf-te-link-attr-reuse-11: 449 8. Considerations for Extended TE Metrics 451 [RFC7471] defines a number of dynamic performance metrics associated 452 with a link. It is conceivable that such metrics could be measured 453 specific to traffic associated with a specific application. 454 Therefore this document includes support for advertising these link 455 attributes specific to a given application. However, in practice it 456 may well be more practical to have these metrics reflect the 457 performance of all traffic on the link regardless of application. In 458 such cases, advertisements for these attributes can be associated 459 with all of the applications utilizing that link, for example, by 460 listing all applications in the Application Bit-Mask. The difference is in the last sentence: the OSPF draft points at how the user can associate the attributes with all the applications...while the ISIS draft just says that the "attributes will be associated with all of the applications". I'm assuming that the ISIS operation is similar: the new sub-TLV would have to include all the appropriate bits in the Application Bit-Mask. Is that a correct assumption, or will ISIS behave differently? Please clarify the text in the ISIS draft. As I mentioned in the thread about draft-ietf-ospf-te-link-attr-reuse, I am starting the IETF Last Call for both documents. We can work on this clarification during that time. Thanks! Alvaro.
- [Lsr] Considerations for Extended TE Metrics (dra… Alvaro Retana