Re: [Lsr] IGP TE Metric Extensions

Robert Raszuk <> Tue, 05 June 2018 15:58 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 2DEE21310AD for <>; Tue, 5 Jun 2018 08:58:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.402
X-Spam-Status: No, score=-1.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.248, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id LQ0mor8PMfTM for <>; Tue, 5 Jun 2018 08:58:49 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:400e:c01::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 686CF130FA0 for <>; Tue, 5 Jun 2018 08:58:49 -0700 (PDT)
Received: by with SMTP id v24-v6so1783575plo.3 for <>; Tue, 05 Jun 2018 08:58:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=8hDk3T0eOSNXvi3RrxJ7oJ5uELm6qekxzW0jt3+v8hE=; b=jHGJOswNiTTe6bf4LTlzXy/npSYYuxiWrd8TrER+Z44n10kPGwcY3jevEf2J8caz8G RmwIqkHq/j1h8DPGtBlrKoC4LPgpPJTGXzgJ3pFd6v5SRW1w5LZg443gxiMhOAxoUYIY 0BRPHJR5tAejsLl8fqWnXn1AdQ0WA6GA3bKnlPaOatsNI8IUmcxUsljhiaYObIZ2iS4h hVr+H3VSyUeYNr9IOn1FZShYr2nYhaaYvF2yxeNuVdwK/QCDGtuXT79mAFJVY0v8/yMi yWe3NqwDbsJFDi35KbPbL6vlsxtgvIpzeHQKHytQ+k+lebP10iHRGqTDaq4p1MwnNZVG 2pYQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=8hDk3T0eOSNXvi3RrxJ7oJ5uELm6qekxzW0jt3+v8hE=; b=DolYHqumvuU5Tauo6UHRwAlZB1cCLrFKZmwGkPg38EEe0xohBhG7uMDHIGKkoUlto6 JnW1F/g+UwNULVNZsNPALo09/F7d6SvCZPhoi/AkFXJT9AEupNijWhBhUNUaoO3S/NkK ksxWZI6spUO+/9bZ9dhS++z6anMuNC6dE6azDYvKxq5CQThlvJwBGzqbj1RaNIWu1X/G PRLNBMH2dd2P+efRwY5yIb2hFi31xUN6X6h//hywuPxUa/l1Ay9XaQOq4c+rWd3Zt2cL 8gp5JQqWNolC7UkH6ABhgktbVITGDT1ADknXR5oBv45YsIK+gQtUTIDhIz3+rgdsbtWd ZW/w==
X-Gm-Message-State: ALKqPwe2ZtYxufIZ5UDksIJK58xrgi+OhNAmCYU7QAJH9roXD3yHMZhQ 63wG/v87B01o9IXnj7cED9jQtKOF5mDRfXZGjlILPcL0
X-Google-Smtp-Source: ADUXVKLh6w+ibk7wA2lMzqtTPRHmTOqpEmI0oVtYrEqFQEv4DpKJejrr0MwuvZRVwjVtgLtG7KfFKULxwhIjqJC5Idk=
X-Received: by 2002:a17:902:4203:: with SMTP id g3-v6mr27672361pld.315.1528214328709; Tue, 05 Jun 2018 08:58:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a17:90a:8402:0:0:0:0 with HTTP; Tue, 5 Jun 2018 08:58:47 -0700 (PDT)
In-Reply-To: <>
References: <> <> <> <> <>
From: Robert Raszuk <>
Date: Tue, 05 Jun 2018 17:58:47 +0200
X-Google-Sender-Auth: nErYlPphs4oQEXx6lqHLZXTrxf4
Message-ID: <>
To: Muthu Arul Mozhi Perumal <>
Cc: "Stefano Previdi (IETF)" <>,, Jeff Tantsura <>
Content-Type: multipart/alternative; boundary="0000000000003419d9056de72035"
Archived-At: <>
Subject: Re: [Lsr] IGP TE Metric Extensions
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Link State Routing Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 05 Jun 2018 15:58:52 -0000


> ​How is the measurement interval and filter coefficients described in the
> draft related to dissemination?​

​It is directly related. If you see the title of the section is:
"Announcement Thresholds and Filters"​

So measurement interval does not intend to describe how often you actually
measure ... it describes a time window where you report the value (which
could consist of many measurements actually taken).

We intentionally left out this part that does not belong to the igp
>> protocol machinery.
> ​Which of the functionalities described in sections 5, 6, 7 of the draft
> belong to the IGP protocol machinery?

​What draft are you talking about ? I was under impression that we are
discussing RFCs here.

​All functionality from sections 5-7 aim to provide machinery to control
stability of protocol operation. It is one how you measure and this is not
part of the RFCs. and completely different what and how you advertised
derived values from those gathered by your measurements. Now keeping in
mind that you do not advertise when you measure but only when you are
allowed by protocol rules it should be easy to see the point which Stefano
made above.