Re: [Lsr] FW: New Version Notification for draft-bonica-lsr-ip-flexalgo-00.txt

Gyan Mishra <hayabusagsm@gmail.com> Sat, 03 October 2020 16:41 UTC

Return-Path: <hayabusagsm@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 69C523A0B50 for <lsr@ietfa.amsl.com>; Sat, 3 Oct 2020 09:41:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.087
X-Spam-Level:
X-Spam-Status: No, score=-2.087 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001] autolearn=unavailable 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 ZhldW98giUyU for <lsr@ietfa.amsl.com>; Sat, 3 Oct 2020 09:41:30 -0700 (PDT)
Received: from mail-vs1-xe35.google.com (mail-vs1-xe35.google.com [IPv6:2607:f8b0:4864:20::e35]) (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 7E1F23A0B55 for <lsr@ietf.org>; Sat, 3 Oct 2020 09:41:30 -0700 (PDT)
Received: by mail-vs1-xe35.google.com with SMTP id e23so2043504vsk.2 for <lsr@ietf.org>; Sat, 03 Oct 2020 09:41:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=A70utf12A17qXckSQBvvmCvWMsN9GislTj6e8+osqJI=; b=ZrjjICR7+ZTRy/8L3wKPUNWoDROV2hfEOfnzKMZBY4wdR9Ttdlo1GfrlihxWWMauwy axAHfLEGMfl2yPnK8S3YNlr/Ozc+PO8grIoGIl/ZkPWjHrQuFrCiZvLr4O2iZZCOwth+ YhWFNwfU0Vujv56dU+pHJAofGO0D7fQtDIVNJRJpOppuy/mznmJURgWXnus3Gcezp6Ew SnKUu2sc1BZjPgJom02OaXnI3igkb57Idk5Ld9vNL1F1cHidBTrmMPU0HXjbDfmsONMV 6pP/j2vFeQk+QOcA1Qt1Qhf6k9LZfHfJXgyn4PFM1+nDckDyRmGPjryGklETVj1mqMbI YBiA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=A70utf12A17qXckSQBvvmCvWMsN9GislTj6e8+osqJI=; b=HKS9eCgLVr/b29PFhXrni7nWCVNOWDxXfU2NF7FPj94b6s46UPOSa6Bm9AZsn0gX6U e+o3hoZZydS4cXU+ni5pM/iCq5SeJc9K1WTLKFYnql7PeX6FgYq39DUrDHDE2gfuugpK x9CM69OUQrhlT5lJwGfpyWzqWxRfVxLP7kOshwfzTM5u2KW0L63AeHd/1tGByyrQR4iF LS47ffJrg3YmbGFOusKc5PrjdRu3uUauXMxsa15t0HQpj2sdONGLUVuJJBXG6DJGl0uz 4eACbn1dAhhgleSqpb4J4adFYErYOkpDoUM66E8hHvj+zPjJv8urKcpYu6dx0KrOrxNV PmUw==
X-Gm-Message-State: AOAM532PCozG63pQ3juPm2fYNuD2C2z3qO36u/M/+0tYkpeJtGISHrbh NVtkGiGJnjNPeSFAlPNh3UiTmwAu5Ytb8bwofx8=
X-Google-Smtp-Source: ABdhPJxCJLUGA6DupNPKia3rJo+KofHMkKoTLa2FghfqEGDyuITzcdjQcefGPNyTiLWJBknKyczF/qO4KypTUW6KRVc=
X-Received: by 2002:a67:e248:: with SMTP id w8mr3913072vse.33.1601743289349; Sat, 03 Oct 2020 09:41:29 -0700 (PDT)
MIME-Version: 1.0
References: <160138654056.12980.329207214151594381@ietfa.amsl.com> <DM6PR05MB63482DBC001DD56BEF6F7311AE320@DM6PR05MB6348.namprd05.prod.outlook.com> <CAKz0y8w5VOf_=baG6UCP8Q9s=VLM2ghT2jhiF5FZNN4JXB23eA@mail.gmail.com> <DM6PR05MB63485389C261CA2E0C08DE50AE330@DM6PR05MB6348.namprd05.prod.outlook.com> <0f85212d-fac7-47ea-a608-4f53061cbf02@Spark> <DM6PR05MB63480E863599BBC810BF334AAE300@DM6PR05MB6348.namprd05.prod.outlook.com> <CABNhwV2+jhjAfxq5FzaukdhCOqXvGCkv75xYWcStN=SCrpni4Q@mail.gmail.com> <f4fdff8b-fe11-cb75-3cd7-7766baedf730@cisco.com> <CB2F6A55-B231-4A2D-821C-D3F2ABE6649E@futurewei.com> <cfae6af4-23d0-44b0-8bb3-f5e631b4c805@Spark> <CABNhwV3MmJeVMhGHqyGzwshSYVijquGsxaNFaryu5mF3j8n_zA@mail.gmail.com> <CAOj+MMFiMsi+1a2Jtn6P2N3KOKjw70bTQYSKxRDrfQCEwVkB+Q@mail.gmail.com>
In-Reply-To: <CAOj+MMFiMsi+1a2Jtn6P2N3KOKjw70bTQYSKxRDrfQCEwVkB+Q@mail.gmail.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Sat, 03 Oct 2020 12:41:18 -0400
Message-ID: <CABNhwV1xQooujd4iSkCeAtbPNWcCr-b+Lh_r00iFd9M3q+9ejQ@mail.gmail.com>
To: Robert Raszuk <robert@raszuk.net>
Cc: Jeff Tantsura <jefftant.ietf@gmail.com>, Peter Psenak <ppsenak=40cisco.com@dmarc.ietf.org>, Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, Yingzhen Qu <yingzhen.qu@futurewei.com>, "lsr@ietf.org" <lsr@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c878ea05b0c6ebf1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/fQeBBzeVdAQEsLZ2iPUkXKKKO9M>
Subject: Re: [Lsr] FW: New Version Notification for draft-bonica-lsr-ip-flexalgo-00.txt
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: Sat, 03 Oct 2020 16:41:33 -0000

On Sat, Oct 3, 2020 at 4:20 AM Robert Raszuk <robert@raszuk.net> wrote:

>
> > Can two nodes that run two different flex algo become ospf or isis
> neighbors?
>
> It is my understanding that those nodes always will become ospf neighbours
> as you still run default topology on all of them. I have not seen a case
> where flex algo topology can be enabled without default topology.
>

    Gyan>. That is what I was thinking as the algo 0 strict spf as the base
algo to provide reachability to all nodes within the domain and all
neighbors are formed between all nodes in the domain to populate IGP rib
providing base connectivity reachability.  So then underneath of that you
can have any subset of nodes out of the superset all top layer domain nodes
level  that can run any other algo desired. Basically creating algo layers
under the top domain wide layer.

I think I am getting it now! 😀

>
> Thx,
> R.
>
> On Sat, Oct 3, 2020 at 2:14 AM Gyan Mishra <hayabusagsm@gmail.com> wrote:
>
>>
>> Hi  Jeff
>>
>> From a domain perspective where you have a group of nodes and associated
>> IP addressed and SID are part of a discrete underlay instance flex algo
>> topology.  On those same set of nodes you could have another topology and
>> associated address and SIDs for a different flex algo.  How this would work
>> is that the topologies would have to be segregated from each other as
>> different MT instances or routing process instances.  Is that correct?
>>
>> Can two nodes that run two different flex algo become ospf or isis
>> neighbors?
>>
>> Kind Regards
>>
>> Gyan
>>
>> On Fri, Oct 2, 2020 at 6:25 PM Jeff Tantsura <jefftant.ietf@gmail.com>
>> wrote:
>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> Hi Yingzhen,
>>>
>>>
>>>
>>>
>>>
>>> Yes, that’s the case.  The most important property of an algo computed
>>> path is that is has to be consecutive, as either SID or IP address
>>> associated with a particular topology is only known within that topology.
>>>
>>>
>>> Looking specifically at Ron’s draft (MPLS could be more complex due to
>>> potential hierarchy) - the prefix itself defines the context(topology) and
>>> must be globally unique, since IPv4 header can’t have any additional
>>> meta-data attached.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> Cheers,
>>>
>>> Jeff
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Oct 2, 2020, 1:15 PM -0700, Yingzhen Qu <yingzhen.qu@futurewei.com>,
>>> wrote:
>>>
>>>
>>> Hi Peter,
>>>
>>>
>>>
>>>
>>>
>>> My understanding of flex-algo is that for traffic destined to a prefix
>>> on a particular algo, it can only be routed on routers belong to that algo,
>>> which also means only routers in that algo calculates how to reach that
>>> prefix and install it into the routing table. It seems to me that using
>>> flex-algo (section 12 of the draft) it's possible to have a loopback
>>> address associated with only one algo, please correct me if I'm missing or
>>> misunderstood something.
>>>
>>>
>>>
>>>
>>>
>>> Thanks,
>>>
>>>
>>> Yingzhen
>>>
>>>
>>>
>>>
>>>
>>> On 10/2/20, 9:43 AM, "Lsr on behalf of Peter Psenak" <
>>> lsr-bounces@ietf.org on behalf of ppsenak=40cisco.com@dmarc.ietf.org>
>>> wrote:
>>>
>>>
>>>
>>>
>>>
>>> Gyan,
>>>
>>>
>>>
>>>
>>>
>>> On 02/10/2020 18:30, Gyan Mishra wrote:
>>>
>>>
>>> All,
>>>
>>>
>>>
>>>
>>>
>>> With SRv6 and IP based flex algo a generic question as it applies to
>>>
>>>
>>> both. Is it possible to have within a single IGP domain different sets
>>>
>>>
>>> of nodes or segments of the network running different algorithms.
>>>
>>>
>>>
>>>
>>>
>>>
>>> absolutely.
>>>
>>>
>>>
>>>
>>>
>>> From
>>>
>>>
>>> both drafts it sounds like all nodes have to agree on same algorithm
>>>
>>>
>>> similar to concept of metric and reference bandwidth all have to have
>>>
>>>
>>> the same style metric and play to the same sheet of music.
>>>
>>>
>>>
>>>
>>>
>>>
>>> all participating nodes need to agree on the definition of the flex-algo
>>>
>>>
>>> and advertise the participation. That's it.
>>>
>>>
>>>
>>>
>>>
>>> If there was
>>>
>>>
>>> a way to use multiple algorithms simultaneously based on SFC or services
>>>
>>>
>>> and instantiation of specific algorithm based on service to be
>>>
>>>
>>> rendered. Doing so without causing a routing loop or sub optimal
>>>
>>>
>>> routing.
>>>
>>>
>>>
>>>
>>>
>>>
>>> you can certainly use multiple algorithms simultaneously and use algo
>>>
>>>
>>> specific paths to forward specific traffic over it. How that is done
>>>
>>>
>>> from the forwarding perspective depends in which forwarding plane you
>>>
>>>
>>> use. Flex-algo control plane is independent of the forwarding plane.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> I thought with flex algo that there exists a feature that on
>>>
>>>
>>> each hop there is a way to specify which algo to use hop by hop similar
>>>
>>>
>>> to a hop by hop policy based routing.
>>>
>>>
>>>
>>>
>>>
>>>
>>> no, there is no hop-by-hop classification, that is problematic and does
>>>
>>>
>>> not scale for high speeds. Classification is done at the ingress only.
>>>
>>>
>>>
>>>
>>>
>>> thanks,
>>>
>>>
>>> Peter
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>>
>>>
>>> Lsr mailing list
>>>
>>>
>>> Lsr@ietf.org
>>>
>>>
>>>
>>> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Flsr&amp;data=02%7C01%7Cyingzhen.qu%40futurewei.com%7C51dd940ab25d4ea19b1b08d866f23b6a%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637372537869296887&amp;sdata=R%2FI%2BAUkcw12FmgDtsh%2FBOL7zLjPF%2BwwRpqwnE2Ndv%2Fg%3D&amp;reserved=0
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>
>> <http://www.verizon.com/>
>>
>> *Gyan Mishra*
>>
>> *Network Solutions A**rchitect *
>>
>>
>>
>> *M 301 502-134713101 Columbia Pike
>> <https://www.google.com/maps/search/13101+Columbia+Pike%C2%A0+Silver+Spring,+MD?entry=gmail&source=g>*Silver
>> Spring, MD
>> <https://www.google.com/maps/search/13101+Columbia+Pike%C2%A0+Silver+Spring,+MD?entry=gmail&source=g>
>>
>>
>>
>> _______________________________________________
>>
>>
>> Lsr mailing list
>>
>>
>> Lsr@ietf.org
>>
>>
>> https://www.ietf.org/mailman/listinfo/lsr
>>
>>
>>
>
> --

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *



*M 301 502-134713101 Columbia Pike *Silver Spring, MD