Re: [Lsr] draft-ietf-lsr-isis-area-proxy-02

Gyan Mishra <hayabusagsm@gmail.com> Thu, 06 August 2020 21:34 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 CA3043A0474 for <lsr@ietfa.amsl.com>; Thu, 6 Aug 2020 14:34:40 -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=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 29qrmXJRUeN8 for <lsr@ietfa.amsl.com>; Thu, 6 Aug 2020 14:34:39 -0700 (PDT)
Received: from mail-vs1-xe30.google.com (mail-vs1-xe30.google.com [IPv6:2607:f8b0:4864:20::e30]) (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 0E36F3A03EE for <lsr@ietf.org>; Thu, 6 Aug 2020 14:34:39 -0700 (PDT)
Received: by mail-vs1-xe30.google.com with SMTP id 1so20150495vsl.1 for <lsr@ietf.org>; Thu, 06 Aug 2020 14:34:38 -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=SNzTxkjjStnQn8A5BaKe9G0/rmzPqpf8xlt40ZsVxyU=; b=aHr2aXwSQXoCFCbzBAVGJssCytt14PAGlwR67BgQOUKv/X1IWu79m8vyZIYGLIgbyX pcAF/RIBDsIs0O0x9fjzU5HhMWAu6snJtHhyOgMtnDWSpT34NPflmMDRVnGVnw2aYrdE OjtnzMGm4W46vOBggGqP5prFLcfrsEaDn5vmly+N4l6DeHYqLxyEyDhvJaYN7MhUQi8v Xvs4Tf1P2tDOXmyPyMa4fQxx5fSQAAZn/CLeCpeqnGAZYif0++j3Eq9acmEFunuMNVru f0Ubdc5OC6sVYK0WG1+uHsr+zSwaTlCMw2hHS32cyDIJvQDbtiQ2dV+JaH1YqmvlnnXD iSbg==
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=SNzTxkjjStnQn8A5BaKe9G0/rmzPqpf8xlt40ZsVxyU=; b=AKRi68Dejhxy2YLRhVVOpm6e+76OA8axUf/+YsGHy2kiVZLCXA7zgZ+qIb4+OmcaiV z8VbQXjGrlKRZ2tbShj7ItE63Oea9YKf58FHc/jh8BJfYIqA/D+xAs8mzuFzp09MbUg9 1SROHpPO6GY7xrQHEm9QCtz68Ypt8YpLcwg9IAedEaHhm/M6lnNdRcr0nL4SeERwBlMq SegLHbx0n9W4YFy6quIGQZkkvnWb12TFh5RFJQvolXuMaKcg+WGlKFvkmvPOidjt8kMe GPLC7lHyB0jaaNU38t/nty5or9JlHdnHdZtuUs/WdSjNQah2MWK7kXbFuQxYWBZQ/20p 7oNA==
X-Gm-Message-State: AOAM530HwvdBCiLtG6qSIYwLAiRRx2SbStUBU3F/SrXadZFCBPgvJaek Ds2rDJIVmJFvJArdtFmscrOF/5zfxo65Jrdd16A=
X-Google-Smtp-Source: ABdhPJwmmX5lbeoXFr/YlpAiH3mSotmBFIFPpJc1rsF7+GWrVEjiMj9rfxJSEFSBYXrhYHJhxIqOpVCTWq8mWft0Cp8=
X-Received: by 2002:a67:fbd1:: with SMTP id o17mr7867297vsr.19.1596749677966; Thu, 06 Aug 2020 14:34:37 -0700 (PDT)
MIME-Version: 1.0
References: <32323_1596545126_5F295866_32323_118_1_53C29892C857584299CBF5D05346208A48F0BB30@OPEXCAUBM43.corporate.adroot.infra.ftgroup> <BY5PR11MB43375CB413060250B336BE64C14A0@BY5PR11MB4337.namprd11.prod.outlook.com> <4558_1596554251_5F297C0B_4558_298_1_53C29892C857584299CBF5D05346208A48F0C59B@OPEXCAUBM43.corporate.adroot.infra.ftgroup> <95A83DB0-A58C-4BD5-AF0B-8EF49D20EB3A@gmail.com> <89F6F8E5-E11D-4A6E-A783-8C9384FE3A1A@cisco.com> <BY5PR11MB4337DB5B017781522AAF9E66C14B0@BY5PR11MB4337.namprd11.prod.outlook.com> <824DFF9C-56E4-4E4F-A249-2E9413D85CC4@gmail.com> <BY5PR11MB4337E1A347464FAD04591D97C14B0@BY5PR11MB4337.namprd11.prod.outlook.com> <2F899EBA-A1F2-4CC5-926C-7215A861E5D7@gmail.com> <BY5PR11MB43378C1841C07A51490A81FBC1480@BY5PR11MB4337.namprd11.prod.outlook.com> <B12E746E-BF84-4D47-98E5-29CB7A95E026@gmail.com>
In-Reply-To: <B12E746E-BF84-4D47-98E5-29CB7A95E026@gmail.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Thu, 06 Aug 2020 17:34:27 -0400
Message-ID: <CABNhwV0BGAuSpTC3hVvdOrp2UTYg+pAbFfVWhwjE-30rYccj-A@mail.gmail.com>
To: Tony Li <tony1athome@gmail.com>
Cc: "Acee Lindem (acee)" <acee@cisco.com>, Bruno Decraene <bruno.decraene@orange.com>, Les Ginsberg <ginsberg@cisco.com>, "lsr@ietf.org" <lsr@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000059ba1c05ac3c4109"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/nU88Be-qLWf0KSskmvD44ZycCUk>
Subject: Re: [Lsr] draft-ietf-lsr-isis-area-proxy-02
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: Thu, 06 Aug 2020 21:34:41 -0000

Hi Tony

See section 3.3.1 of RFC 8402 SR Architecture

https://tools.ietf.org/html/rfc8402#section-3.3.1

It has a nice graphical explanation of SR-MPLS Anycast usage.

The concept of Anycast SID is similar to Multicast group GDA conceptually
and similar to IGP routing anycast construct of proximity routing but more
like the former GDA based routing.

Basically you can have a group of nodes in the SR domain that can be
assigned an Anycast SID A and another group an Anycast SID B for the nodes
and a common group outer label Anycast SID is assigned to forward to the
Group of nodes represented by the Anycast SID.  The inner label is
basically a common label to forward to the group of nodes.

You can think of Anycast as similar to SR-TR prefix sid steering ECMP
pathing where all paths are active to get to the unicast destination.

In this case its all paths active but now to a pseudo multicast like
“anycast sid” group destination.

The concept of Anycast SID exists with SRv6 as well.

I think to your point I am not sure why it matters and can the Area prefix
be either unicast or Anycast.  As far at the area leader if that is a
single node then the node sid could be utilized and if the area leader is a
group or more then one node then a Anycast sid could be utilized.  I think
flexibility would be best so it can be either as you pointed out.

Kind Regards


Gyan

On Thu, Aug 6, 2020 at 12:32 PM Tony Li <tony1athome@gmail.com> wrote:

>
>
> Les,
>
> * There then remains the question as to whether the “Area Prefix” is
> anycast or unicast i.e., is it common to all IERs or is it unique to
> whomever gets elected Area Leader?*
>
>
> Does it matter? We have no clear semantics for this prefix. A difference
> that makes no difference is no difference.
>
> *[Les:] This question needs to be directed at those who prefer the Area
> Prefix approach. It matters as it impacts configuration and advertisement
> semantics. An anycast prefix is NOT a Node Prefix.*
> *And it impacts how traffic is forwarded into the area.*
>
>
>
>
> How so?  Traffic will be directed to the SID value (modulo PHP).
> *[Les3:] If the prefix is private to a single router then traffic has to
> pass through that router. If it is anycast the traffic could arrive at any
> one of the routers supporting the anycast address.*
>
>
>
> I must be missing something. My understanding of SR is that you forward
> based on the label.  Please educate me.
>
> Tony
>
> _______________________________________________
> 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