IETF Logo Mail Archive

Re: [Isis-wg] ISIS SR Flexible Algorithm (Resending with alias correction)

Tony Przygienda <tonysietf@gmail.com> Mon, 20 November 2017 21:11 UTC

Return-Path: <tonysietf@gmail.com>
X-Original-To: isis-wg@ietfa.amsl.com
Delivered-To: isis-wg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB647128CD5; Mon, 20 Nov 2017 13:11:51 -0800 (PST)
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 uFA5iP0CoUE5; Mon, 20 Nov 2017 13:11:50 -0800 (PST)
Received: from mail-wm0-x22b.google.com (mail-wm0-x22b.google.com [IPv6:2a00:1450:400c:c09::22b]) (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 E38F8120713; Mon, 20 Nov 2017 13:11:46 -0800 (PST)
Received: by mail-wm0-x22b.google.com with SMTP id 128so12919947wmo.3; Mon, 20 Nov 2017 13:11:46 -0800 (PST)
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=4rsFb8fCzPCw1oxS2CnY2jcLcS3CCQHcU7We+weZ6Bw=; b=bpJsrYNYS9qXqJKee7EdsEkofWZIwK0UpCKma7mVfwpHIlNTYho2AdNNLRj1GE+d5a 5iT2E7OkHIOGMuN4VfixcY93lFBOUSP+s8ojRZXgLhkNqDnwQ+w2LC/hlimUhDqFoQfE PNRIOPsz0Qk48304Qmuy4sV1bbzuZ5n/ejx/ZcxFmBBFAoAajU3sSGJA17ylX2u3WRUJ cknYt2rNmLK+7QPT3Hoomla/A4HZO6BCb1dMfjMns7OdfD9hNmobPuKItHAPFaXdYCfA 7uiAsGwc3SHKv0e5TtU3Be1jj3m01LdWrB/tKg0hazs2VRMzbMfKs8yuo9b2CSPPxvMI 6u9w==
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=4rsFb8fCzPCw1oxS2CnY2jcLcS3CCQHcU7We+weZ6Bw=; b=oAZ9PrrxABttEolA/u6T7D8dHi+zpi+ywPRtnCyHZger95Xr3U/2bJmOcmj3Uco3VX tLRQ9lWvIn2SB5zCzwe5akoJ5KehuwtF9mXK7kkc4SXR9S4Dkk0/HJ3p/WmGWtnNB3mQ Lm9IBOCEJDtF914f6SJjPC1Cv+3iS9fCifZ91Z96SB6hU9DsIHfAYM1GCCPGOgttQtmF oc+xtzpp0z0Pnbzsf0XbqEquNvdXPEFxoCU7vfU1D1R8f+wMjL/1uS5xM2eU0MxJzq1J nd0xcERCV2KIUlKkPZAnW1hc3cZhr/HafvXgWopT2x7Z0N6m56CGZJOEUpiyjvbdyKXD uKWQ==
X-Gm-Message-State: AJaThX5a8OibzrpsFdd4CCngzD1P7+D9Dtaos+b8gzIlfDDZgjTDK9HL 4vaDv2t4TuxZ3vL3i/Ltd0cg1PZPRYkeFiU9Mqg=
X-Google-Smtp-Source: AGs4zMYG+2NBsXfn81gLv6+hXpW7i1dGTh1WbafHDX936V4mPJL9+lErnmUBQTh9l7MSDx/phAmrIgP8WGx0wFR6b5s=
X-Received: by 10.80.245.181 with SMTP id u50mr21253614edm.171.1511212305512; Mon, 20 Nov 2017 13:11:45 -0800 (PST)
MIME-Version: 1.0
Received: by 10.80.164.199 with HTTP; Mon, 20 Nov 2017 13:11:05 -0800 (PST)
In-Reply-To: <D63886A4.DA829%acee@cisco.com>
References: <D63886A4.DA829%acee@cisco.com>
From: Tony Przygienda <tonysietf@gmail.com>
Date: Mon, 20 Nov 2017 13:11:05 -0800
Message-ID: <CA+wi2hPsF1NJTLH_D1X5jpCGBhc0U9yoKU1cG3UNnwQbiUwWxw@mail.gmail.com>
To: "Acee Lindem (acee)" <acee@cisco.com>
Cc: "draft-hegdeppsenak-isis-sr-flex-algo@ietf.org" <draft-hegdeppsenak-isis-sr-flex-algo@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>
Content-Type: multipart/alternative; boundary="001a114e6480a67e1c055e708844"
Archived-At: <https://mailarchive.ietf.org/arch/msg/isis-wg/VJwGIkwRRgNy1XR3SoXsS5HqXqQ>
Subject: Re: [Isis-wg] ISIS SR Flexible Algorithm (Resending with alias correction)
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/isis-wg/>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Nov 2017 21:11:52 -0000

So, it seems that there will be a new draft with 242 covering all
algorithms (i.e. no MT specific algo advertisement anymore).

Then I thought each MT advertises which Flex it supports. Is the assumption
that you can run multiple algorithms per MT? How would you otherwise have a
two-algorithms-to-same-prefix problem?

Is there some kind of conceptual model of FlexAlgo, i.e. how many of what
associated with how  many of the other (MT to algo, algo to protocol
instance etc) ...

-- tony

On Mon, Nov 20, 2017 at 10:19 AM, Acee Lindem (acee) <acee@cisco.com> wrote:

> Hi Shraddha, Peter, et al,
>
> The comment on the draft I had was that the conflict case where two ISIS
> routers advertise the same multi-homed prefix with a different algorithm
> needs to be covered. I wouldn’t try and optimize for this and would just do
> whatever is simplest but avoids loops (e.g., log the situation and prefer
> the path computed with the lowest numbered algorithm).
>
> Thanks,
> Acee
>
> _______________________________________________
> Isis-wg mailing list
> Isis-wg@ietf.org
> https://www.ietf.org/mailman/listinfo/isis-wg
>
>

v2.23.0 | Report a Bug | By Email