Re: [Lsr] IGP TE Metric Extensions

Muthu Arul Mozhi Perumal <muthu.arul@gmail.com> Tue, 05 June 2018 12:21 UTC

Return-Path: <muthu.arul@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 4E443130FF8 for <lsr@ietfa.amsl.com>; Tue, 5 Jun 2018 05:21:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 df9aEN5-lYVP for <lsr@ietfa.amsl.com>; Tue, 5 Jun 2018 05:21:52 -0700 (PDT)
Received: from mail-it0-x22f.google.com (mail-it0-x22f.google.com [IPv6:2607:f8b0:4001:c0b::22f]) (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 EB7EF130FEA for <lsr@ietf.org>; Tue, 5 Jun 2018 05:21:51 -0700 (PDT)
Received: by mail-it0-x22f.google.com with SMTP id j186-v6so3035581ita.5 for <lsr@ietf.org>; Tue, 05 Jun 2018 05:21:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=9KHcGPJPHJfSQXRWMefFJqxZvbhhDUgoFSlYGXWqUUc=; b=YhzJx0qDTJdcqPBCZGYV1VBtOjG5dZr6YJJg6dqm73AX6TpxA9/dUojt+lNT2HGh/l AXIKYgbLL9Md2jxXtYJ+eqUQfuo9VNqfzPWaAxO03Ezbsu00E4XsOnqoFiYNaBKjLXlu 1ykKrkoRzFxDWjxnlqznZi+6LPWC7dqjPWnS0s/zrmlKXUONi6d3iOkYUvc75JVllgZW eO//20baJ9/0tdzlPli1hZkE3y5ZVGwtKY4PDi1X4ElkhtLUCPRTMyrCYExoF6QFPsI8 wxcJ3+PSOQyg+Wds/xZ2UZTMiB4CDQtSYCdM1UClGFUvuij4cq36q7V/z3Wmsq2XW3jE x5WA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=9KHcGPJPHJfSQXRWMefFJqxZvbhhDUgoFSlYGXWqUUc=; b=bHCSn5QTCX8kXTU8eENtcN/EG8Bze2hW8c10vMl/IVkhQxgdg6oyNmEox9Z9pqzAlU r+RQIdYe6HSgejyETyp7yUUtq/ai1+UIk721YzwPKs5SJRYDttdx6aVIplpGSH1KHSlo OF+69jci0tMAWlJ1qHjXNUXx7D/G3jTSk2Ig54aF5NyPhqpd5OwPspeCTxjbwDuN1RUT rvOAcFtCzXaRP6N479zRnY6zZam0n0kwS3+d+r/GwqOANQh6VN1jS89z0sbk7gZqTtwL rOw/gxvzC9gVrm3TUTya4bN5Gf/huUDQJaMqbb3nbL8A6T56S0/7uy0HSDNacfB9BZvx XDWA==
X-Gm-Message-State: ALKqPwcYTTzivHegced4N7qzhIbtuKBoBO0oaFy++pVof6TtpxpuUKTa fcB1WJGgrt5PVNKcvpajHJ5UwsbPzbQspZiu7Z0GXw==
X-Google-Smtp-Source: ADUXVKKViFDaaHDL6gHtEr0J3KhJQpik1SPS/ytVuXYr+8lytk1xFRtDVeG7A3azGTSb/GdVmlHaKNvkLOlc4/YfxVo=
X-Received: by 2002:a24:c146:: with SMTP id e67-v6mr18208479itg.70.1528201311226; Tue, 05 Jun 2018 05:21:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a02:9802:0:0:0:0:0 with HTTP; Tue, 5 Jun 2018 05:21:50 -0700 (PDT)
In-Reply-To: <b5583439198442cdab833a798985c377@XCH-ALN-008.cisco.com>
References: <CAKz0y8zTE_ZkN6_MdXF0hxoRJG81TpBJAk9vtvjYmzWpY6=FHw@mail.gmail.com> <B33C32CE-0EDA-41C9-B1A6-62E8DBA0E7B2@gmail.com> <CAKz0y8yGWg5=ZGyTcWiRSJQFKF7brZddnpVhMPk6GwmhhQr3Uw@mail.gmail.com> <CAJp-iyW2RRQOTfpdh4xLLqUK_xPwqLdDU7ijBPmDSXLn=HVBMQ@mail.gmail.com> <CAKz0y8wnP6PsJPOCTmXOzmHBs5X=2PuXCbgLJ_BWUm3XhNmURw@mail.gmail.com> <cb14fd79505a48f6b9fa57be5354673a@XCH-ALN-008.cisco.com> <CAKz0y8w7cO1AGZxp83Rf-_TvjeEz6zEjsB5UBLmAsC17c34e2w@mail.gmail.com> <b5583439198442cdab833a798985c377@XCH-ALN-008.cisco.com>
From: Muthu Arul Mozhi Perumal <muthu.arul@gmail.com>
Date: Tue, 5 Jun 2018 17:51:50 +0530
Message-ID: <CAKz0y8whN=KSR45V6kZ=TvCNwx=BG00v2xz=Dan2yO-jhbEnSg@mail.gmail.com>
To: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
Cc: "Stefano Previdi (IETF)" <s@previdi.net>, "lsr@ietf.org" <lsr@ietf.org>, Jeff Tantsura <jefftant.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="0000000000004d112c056de418d1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/PPosgniiocZDVFyX07PdtUxQl_g>
Subject: Re: [Lsr] IGP TE Metric Extensions
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.26
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: Tue, 05 Jun 2018 12:21:56 -0000

If these are only implementation specific aspects and shouldn't get into
the draft, what is the point of sections 5,6,7? Why would it hurt to say
what is generally expected to be part of the protocol machinery and what is
not?

BTW, any known implementation for RFC 7810, also supporting sections 5,6,7?

Regards,
Muthu

On Tue, Jun 5, 2018 at 5:33 PM, Ketan Talaulikar (ketant) <ketant@cisco.com>
wrote:

> Hi Muthu,
>
>
>
> These are implementation specific aspects and I am not sure if this is
> something that the draft should be getting into.
>
>
>
> Thanks,
>
> Ketan
>
>
>
> *From:* Muthu Arul Mozhi Perumal <muthu.arul@gmail.com>
> *Sent:* 05 June 2018 17:19
> *To:* Ketan Talaulikar (ketant) <ketant@cisco.com>
> *Cc:* Stefano Previdi (IETF) <s@previdi.net>et>; lsr@ietf.org; Jeff Tantsura
> <jefftant.ietf@gmail.com>
>
> *Subject:* Re: [Lsr] IGP TE Metric Extensions
>
>
>
> Sounds reasonable to me..
>
>
>
> Adding a clarification note in the draft would be useful, IMHO.
>
>
>
> Regards,
>
> Muthu
>
>
>
> On Tue, Jun 5, 2018 at 5:00 PM, Ketan Talaulikar (ketant) <
> ketant@cisco.com> wrote:
>
> Hi Muthu,
>
>
>
> The Sections 5, 6 and 7 of these drafts are critical as it impacts the IGP
> protocol operation and stability though it is not an integral part of the
> IGP protocol machinery. This functionality in a system, whether achieved in
> the IGP/measurement/some-other module, is an implementation specific aspect.
>
>
>
> To answer your question, these aspects may be implemented outside the core
> IGP module and the IGPs simply flood these while satisfying the aspects
> specified in the document.
>
>
>
> Thanks,
>
> Ketan
>
>
>
> *From:* Lsr <lsr-bounces@ietf.org> *On Behalf Of *Muthu Arul Mozhi Perumal
> *Sent:* 05 June 2018 16:42
> *To:* Stefano Previdi (IETF) <s@previdi.net>
> *Cc:* lsr@ietf.org; Jeff Tantsura <jefftant.ietf@gmail.com>
> *Subject:* Re: [Lsr] IGP TE Metric Extensions
>
>
>
>
>
> ​Please see inline..​
>
>
>
> On Fri, Jun 1, 2018 at 2:34 AM, Stefano Previdi (IETF) <s@previdi.net>
> wrote:
>
>
>
> On Thu, May 31, 2018, 6:15 PM Muthu Arul Mozhi Perumal <
> muthu.arul@gmail.com> wrote:
>
> Thanks, Jeff. Would be good to have this clarified in
>
> ​​
>
> draft-ginsberg-isis-rfc7810bis. My original message seems to have been
> stripped off, so including it again for the lsr list..
>
>
>
> ​Both RFC 7810 and RFC 7471 say that:
>
>
>
>    The measurement interval, any filter coefficients, and any
>
>    advertisement intervals MUST be configurable per sub-TLV.
>
>
>
>    Additionally, the default measurement interval for all sub-TLVs
>
>    SHOULD be 30 seconds.
>
>
>
> However, both RFCs initially say that they only describe mechanisms for
> disseminating performance information and methods of measurements is
> outside their scope.
>
>
>
> Moreover, for a first time reader, it seems to suggest that the
> measurement interval and filter coefficient must be supported and
> configurable under the IGP.
>
>
>
>
>
> No. This is not suggested in any form.
>
> It is clearly indicated that the draft does not deal with measurements
> which means no recommendation is made.
>
>
>
>
>
> In a system supporting multiple IGPs, I would expect that they be
> implemented outside the IGP and the IGPs just disseminate the information
> provided to them.
>
>
>
> Thoughts, especially from an implementation standpoint?
>
>
>
>
>
> Again, the draft is only about dissemination, not measurements..
>
>
>
> ​How is the measurement interval and filter coefficients described in the
> draft related to dissemination?​
>
>
>
> ​   The measurement interval, any filter coefficients, and any
>
>    advertisement intervals MUST be configurable per sub-TLV.
>
>
>
>    Additionally, the default measurement interval for all sub-TLVs
>
>    SHOULD be 30 seconds.​
>
>
>
> If your question is related to configuration and implementation of
> measurements, well it will not be addressed by this draft.
>
>
>
> 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?
>
>
>
> Regards,
>
> Muthu
>
>
>
>
>
> s.
>
>
>
>
>
>
>
> Regards.
>
> Muthu
>
>
>
> On Thu, May 31, 2018 at 11:37 AM, Jeff Tantsura <jefftant.ietf@gmail.com>
> wrote:
>
> Muthu,
>
> LSR would be a more suitable list to post to, CCed.
>
> Regards,
> Jeff
>
> > On May 30, 2018, at 18:06, Muthu Arul Mozhi Perumal <
> muthu.arul@gmail.com> wrote:
> >
> > Muthu
>
>
>
> _______________________________________________
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr
>
>
>
>
>