IETF Logo Mail Archive

Re: [Lsr] Publication has been requested for draft-ietf-lsr-ip-flexalgo-06

Robert Raszuk <robert@raszuk.net> Tue, 17 May 2022 10:10 UTC

Return-Path: <robert@raszuk.net>
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 A2887C14F741 for <lsr@ietfa.amsl.com>; Tue, 17 May 2022 03:10:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=raszuk.net
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rAh0TQllH75H for <lsr@ietfa.amsl.com>; Tue, 17 May 2022 03:10:48 -0700 (PDT)
Received: from mail-vs1-xe2e.google.com (mail-vs1-xe2e.google.com [IPv6:2607:f8b0:4864:20::e2e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0646FC14F749 for <lsr@ietf.org>; Tue, 17 May 2022 03:10:47 -0700 (PDT)
Received: by mail-vs1-xe2e.google.com with SMTP id i186so18166891vsc.9 for <lsr@ietf.org>; Tue, 17 May 2022 03:10:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=lwE3JknTWUuRy4NLjIw4DGPV6wXwruxhU2zx6CUNEjc=; b=LTXcEFZNcEEDWttvFofPnlkNo1loMX8VCj8zqiBFzql5dUc5tXwez8yYZGQ/+BZi4x DuPUB+cTNnTXxbeBaaReot6lQc+NB+1cWCrn26XDFYRknk9I18LhuCWuWC1UNgKnwTc/ SnE3UkdCq7a+Cu1mbljT5qw/kS33VNy1j3B1vpO/J8OCK1hayDGfuWdUrWphOBKi1Lvx oc32Hdoxp7/51HYYUs5W+igjTGYDRoFFryTOy6c+HeVphB+8IOQLxjvHW1EaQsaexKAn uRqfTtRMX2hUQjgIPmKMycw1eCwhbYs+2Yon/yHvUC5Z+ELsqidmTKlGaMQr2joQvHXq 9iqA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=lwE3JknTWUuRy4NLjIw4DGPV6wXwruxhU2zx6CUNEjc=; b=JVzrzsN2p5106yQinf17JrKEmMXy1/99wd84AFQtMYrkVty9QPrTtXuKqOyGXpk5KE rDE5T20Pz61HUPpFU1DLyKdjLAht8pRuuk1ispvzQ9pC9A4/anNY9cVHUXId87BIyLWU AOwKeVAo1gZx3SQUUYcxi1hNDsKjmZcbemWNojMquFkqGOBKIc1Ju5/KvXcbX+o7y9xW O11Z6LuLtPP4BC3ooz9ZmXVw2QkU7xIEOe+ccm3FceW1sobUxY0Gw+WVoyCAfJ7sFBH0 CAdPQZq/cgfrJfN2iIuXfpENeYESgPSP7MNDQRQGK8VjH7LukOATkGP9MH7qead1q1WV O8UA==
X-Gm-Message-State: AOAM531Ds9Qt2Mn+wzPHNXJrjoerbej5NAxHiG/ePOrNlA2Gs7NfBeOh GLCjgaU1x6GOR5gPkxhCPvkQ0FZQeDiVAW/043TTDWpVPTc=
X-Google-Smtp-Source: ABdhPJyi30A2qQr6NlNMpPIx+atv3NhkeBHbVggVAZo3u2U6Effhf0/WHzqAiQ0H0B3SQ+NS9UxG867KlKdt/imZTdI=
X-Received: by 2002:a05:6102:1629:b0:32d:33c3:d815 with SMTP id cu41-20020a056102162900b0032d33c3d815mr8503826vsb.15.1652782246686; Tue, 17 May 2022 03:10:46 -0700 (PDT)
MIME-Version: 1.0
References: <165270816129.62374.13329927223902426661@ietfa.amsl.com> <CAOj+MMGoNOLMW0r3-JpMxyGQFv6ehKR5o4w4eqWQT8VmT=MO5A@mail.gmail.com>
In-Reply-To: <CAOj+MMGoNOLMW0r3-JpMxyGQFv6ehKR5o4w4eqWQT8VmT=MO5A@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Tue, 17 May 2022 12:11:07 +0200
Message-ID: <CAOj+MMGhe27QynC7JB2vxkiKeXxtKXJxeKzd5SeP6nHs8JL0zg@mail.gmail.com>
To: lsr <lsr@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b487b605df325ac2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/WjIF18_h6DFO0l_huoZjxqbWqOo>
Subject: Re: [Lsr] Publication has been requested for draft-ietf-lsr-ip-flexalgo-06
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.34
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, 17 May 2022 10:10:51 -0000

Actually I would like to further clarify if workaround 1 is even doable ...

It seems to me that the IP flexalgo paradigm does not have a way for more
granular then destination prefix forwarding.

So if I have http traffic vs streaming vs voice going to the same load
balancer (same dst IP address) there seems to be no way to map some
traffic (based on say port number) to take specific topology.

That's pretty coarse and frankly very limiting for applicability of IP
flex-algo. If I am correct the draft should be very explicit about this
before publication.

Kind regards
R.

On Tue, May 17, 2022 at 12:01 PM Robert Raszuk <robert@raszuk.net> wrote:

> Folks,
>
> A bit related to Aijun's point but I have question to the text from the
> draft he quoted:
>
>    In cases where a prefix advertisement is received in both a IPv4
>    Prefix Reachability TLV and an IPv4 Algorithm Prefix Reachability
>    TLV, the IPv4 Prefix Reachability advertisement MUST be preferred
>    when installing entries in the forwarding plane.
>
> Does this really mean that I can not for a given prefix say /24 use
> default topology for best effort traffic and new flex-algo topology for
> specific application ?
>
> Is the "workaround 1" to always build two new topologies for such /24
> prefix (one following base topo and one new) and never advertise it in base
> topology ?
>
> Is the "workaround 2" to forget about native forwarding and use for
> example SR and mark the packets such that SID pool corresponding to base
> topology forwarding will be separate from SID pool corresponding to new
> flex-algo topology ?
>
> Many thx,
> Robert
>
>
> ---------- Forwarded message ---------
> From: Acee Lindem via Datatracker <noreply@ietf.org>
> Date: Mon, May 16, 2022 at 3:36 PM
> Subject: [Lsr] Publication has been requested for
> draft-ietf-lsr-ip-flexalgo-06
> To: <jgs@juniper.net>
> Cc: <acee@cisco.com>, <iesg-secretary@ietf.org>, <lsr-chairs@ietf.org>, <
> lsr@ietf.org>
>
>
> Acee Lindem has requested publication of draft-ietf-lsr-ip-flexalgo-06 as
> Proposed Standard on behalf of the LSR working group.
>
> Please verify the document's state at
> https://datatracker.ietf.org/doc/draft-ietf-lsr-ip-flexalgo/
>
>
> _______________________________________________
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr
>

v2.23.0 | Report a Bug | By Email