Re: [Idr] BGP-LS alternatives - problems and solutions
Gyan Mishra <hayabusagsm@gmail.com> Thu, 30 June 2022 06:57 UTC
Return-Path: <hayabusagsm@gmail.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71192C15AAC7 for <idr@ietfa.amsl.com>; Wed, 29 Jun 2022 23:57:33 -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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, T_SCC_BODY_TEXT_LINE=-0.01, 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=gmail.com
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 4SD1Q6H4OcwD for <idr@ietfa.amsl.com>; Wed, 29 Jun 2022 23:57:29 -0700 (PDT)
Received: from mail-pl1-x62d.google.com (mail-pl1-x62d.google.com [IPv6:2607:f8b0:4864:20::62d]) (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 A391CC15D885 for <idr@ietf.org>; Wed, 29 Jun 2022 23:57:29 -0700 (PDT)
Received: by mail-pl1-x62d.google.com with SMTP id jb13so16202582plb.9 for <idr@ietf.org>; Wed, 29 Jun 2022 23:57:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=btUxQpE56dwtE9KjNhyJkZaqHnFwbGNrPbwAe5UsdRI=; b=S79Ec3Sq2zAUidNi0RjalLXzvClHWLhLECFEiVVdOl1nnH9TmDc+fX3StOwASmRlW/ jkFBmcaMptUifKEto9U2vg+3rAQJBJd1O7EAa2CRB22tpL4kAqH75q86DxahdTLX0/5w cwExjxpV4cpWzGUDlUm2ru2OirTD9b5x4X1RqAGevpfS0VsY1Bi5ekVlJ6G5xHjO8m7Q tY6y+4jo4NNvp5uGbRQlECN8sX4a+47GAmJvR8sdYjg70DeaciiEj0ht54HQ3lZz4yub 4AIn34PUoZI3tuWnP6z7beaSZwLvGnj9InMljosracW0tpoNwr+HIZPwA0N5Qcbdn2Fd rwCA==
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:cc; bh=btUxQpE56dwtE9KjNhyJkZaqHnFwbGNrPbwAe5UsdRI=; b=fZTmqRxDHfaMhXpdBRMj8+jbiwQd05xBW41uXgU+MzfkHIowKgb0gfC5Q0nC9o73GO DCGcp4jZkFhCcVaIK3HBwoKy4RRDLV+cLAM1/nEe8XEGVkZUCmCmp71tS6AE/liJ9AWU sphKU6MwbG/Ck0He5vPW9qqRRv+vUMMt+ucRdiqnk5YfbZeuEnQdJ5d/TtanCfjHGBTE amSjyt/12ELJuZsXe3ChwS96S3kor/aojiRi8IhQprrMYD5w2l32c2RchsZ4/AXdMKpv kgT2ymiLzLyIj9NVxcTT5CGX0AFHu1TZtDZpcE8YWj0A7+k3ugBJXoRN/OvVLvzYGoxo S3+Q==
X-Gm-Message-State: AJIora/JQqAv5OiqZjfDX8IHxBUnrtoVB9o/e/PQkokHvbercVNuiy80 rf5pA92OKIhn8gvBlH7sq5xHFEDGNezhArqbEJ8=
X-Google-Smtp-Source: AGRyM1vCLEbVthNjKENx+Xy3T7Et9pz4Yq9NUnfj7VOcg/xUVOhfFgjc+lzfgMQYFWaHmeIk1KsZVNaar8SzmoqcbAA=
X-Received: by 2002:a17:903:240b:b0:16b:8e84:f22d with SMTP id e11-20020a170903240b00b0016b8e84f22dmr13545701plo.128.1656572248934; Wed, 29 Jun 2022 23:57:28 -0700 (PDT)
MIME-Version: 1.0
References: <CAB75xn4z6qjFX2qDhZ65wVBdU1HXibOv75dXxUnGi-checy87g@mail.gmail.com> <16EE998C-18DF-4ADE-92C5-BC360B9ABC3E@tsinghua.org.cn>
In-Reply-To: <16EE998C-18DF-4ADE-92C5-BC360B9ABC3E@tsinghua.org.cn>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Thu, 30 Jun 2022 02:57:17 -0400
Message-ID: <CABNhwV26kZygdNty7hJATjF4Ex0yAN2RP3Cx3J0hXy9ZkFechA@mail.gmail.com>
To: Aijun Wang <wangaijun@tsinghua.org.cn>
Cc: Dhruv Dhody <dhruv.ietf@gmail.com>, Susan Hares <shares@ndzh.com>, idr@ietf.org
Content-Type: multipart/alternative; boundary="00000000000071540605e2a4c8a1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/RpjqWk5x3P8RBh6lnE5iH9aqULw>
Subject: Re: [Idr] BGP-LS alternatives - problems and solutions
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2022 06:57:33 -0000
I support the PCEP-LS as an BGP-LS alternative using NBI to build network graph using PCEP Centralized SDN/PCE controller. https://datatracker.ietf.org/doc/html/draft-dhodylee-pce-pcep-ls-23 This allows BGP to remain clean “routing only” protocol and not overloaded by “non routing” related data. PCEP-LS may also be able to solve existing issues with BGP-LS inherent to BGP-LS. Kind Regards Gyan On Thu, Jun 30, 2022 at 2:46 AM Aijun Wang <wangaijun@tsinghua.org.cn> wrote: > I support to distribute the futures IGP load for controller via the > PCEP-LS. > The information for controller should be distributed via the north-bound > protocol, for example PCEP. > PUB/SUB model can also be implemented via the existing PCEP protocol. > > BGP should be used remain in its original east-west domain. > > Aijun Wang > China Telecom > > On Jun 30, 2022, at 14:23, Dhruv Dhody <dhruv.ietf@gmail.com> wrote: > > > > Thanks Muthu, > > Let me add some introduction - PCEP-LS [1] specify a new message, a new > object, and some container TLVs but reuses the BGP-LS sub-TLVs inside. It > is a particularly good alternative when PCECC [2][3] is in use and for > optical networks [4]. > > Thanks, > Dhruv > > [1] https://datatracker.ietf.org/doc/draft-dhodylee-pce-pcep-ls/ > [2] https://datatracker.ietf.org/doc/rfc8283/ > [3] https://datatracker.ietf.org/doc/rfc9050/ > [4] https://datatracker.ietf.org/doc/draft-lee-pce-pcep-ls-optical/ > > On Thu, Jun 30, 2022 at 11:30 AM Muthu Arul Mozhi Perumal < > muthu.arul@gmail.com> wrote: > >> Hi, >> >> A comment inline.. >> >> On Thu, Jun 30, 2022 at 3:18 AM Susan Hares <shares@ndzh.com> wrote: >> >>> IDR WG continues to strive to create BGP technology that >>> >>> a) enables the BGP protocols to solve customer problems, >>> >>> b) enables implementers to create efficient code, and >>> >>> c) helps to create a stable and manageable routing infrastructure. >>> >>> >>> >>> In our striving, it is sometimes useful to consider >>> >>> whether a technology can be improved. >>> >>> In our last WG adoption call for a BGP-LS feature, >>> >>> the question was raised whether there were better >>> >>> alternatives to BGP-LS. >>> >>> >>> >>> IDR focus is on specific BGP solutions for specific >>> >>> problems. Below I’ve given you a sample format. >>> >>> >>> >>> If we have enough problem/solutions, we’ll hold an interim >>> >>> for further discussions. >>> >>> >>> >>> Cheers, Sue >>> >>> >>> >>> ==================== >>> >>> >>> >>> Problem: BGP-LS original authors wanted to expose LSR (OSPF and ISIS) >>> >>> Information via BGP >>> >>> >>> >>> Use case: Wide Area networks with multiple IGP domains >>> >>> connected by BGP >>> >>> >>> >>> Solution: draft-li-lsr-droid-00.txt >>> >>> Benefits: Allows clear delineation between information >>> >>> Distribution and routing. Frees up routing protocols to >>> >> >> There is also an experimental PCEP-LS: draft-dhodylee-pce-pcep-ls >> >> Regards, >> Muthu >> >>> Just do routing. >>> >>> >>> >>> Deficit/Benefit: >>> >>> 1. New protocol must be deployed along with >>> >>> ISIS, OSPF and BGP. >>> >>> 2. Interactions between BGP-LS >>> >>> >>> >>> Open issues: What are potential error conditions for >>> >>> Protocol interactions (ISIS/OSPF to DROID)? >>> >>> >>> >>> >>> _______________________________________________ >>> Idr mailing list >>> Idr@ietf.org >>> https://www.ietf.org/mailman/listinfo/idr >>> >> _______________________________________________ >> Idr mailing list >> Idr@ietf.org >> https://www.ietf.org/mailman/listinfo/idr >> > _______________________________________________ > Idr mailing list > Idr@ietf.org > https://www.ietf.org/mailman/listinfo/idr > > _______________________________________________ > Idr mailing list > Idr@ietf.org > https://www.ietf.org/mailman/listinfo/idr > -- <http://www.verizon.com/> *Gyan Mishra* *Network Solutions A**rchitect * *Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>* *M 301 502-1347*
- [Idr] BGP-LS alternatives - problems and solutions Susan Hares
- Re: [Idr] BGP-LS alternatives - problems and solu… Muthu Arul Mozhi Perumal
- Re: [Idr] BGP-LS alternatives - problems and solu… Dhruv Dhody
- Re: [Idr] BGP-LS alternatives - problems and solu… Aijun Wang
- Re: [Idr] BGP-LS alternatives - problems and solu… Gyan Mishra
- Re: [Idr] BGP-LS alternatives - problems and solu… Robert Raszuk
- Re: [Idr] BGP-LS alternatives - problems and solu… guntervandeveldecc@icloud.com
- Re: [Idr] BGP-LS alternatives - problems and solu… Robert Raszuk
- Re: [Idr] BGP-LS alternatives - problems and solu… olivier.dugeon
- Re: [Idr] BGP-LS alternatives - problems and solu… Robert Raszuk
- Re: [Idr] BGP-LS alternatives - problems and solu… Gyan Mishra
- Re: [Idr] BGP-LS alternatives - problems and solu… Muthu Arul Mozhi Perumal
- Re: [Idr] BGP-LS alternatives - problems and solu… guntervandeveldecc@icloud.com
- Re: [Idr] BGP-LS alternatives - problems and solu… Jeffrey Haas
- Re: [Idr] BGP-LS alternatives - problems and solu… Robert Raszuk
- Re: [Idr] BGP-LS alternatives - problems and solu… Tony Przygienda
- Re: [Idr] BGP-LS alternatives - problems and solu… Gyan Mishra
- Re: [Idr] BGP-LS alternatives - problems and solu… Jeffrey Haas