Re: [Idr] BGP flooding and AS-PATH

Robert Raszuk <robert@raszuk.net> Mon, 11 March 2019 11:38 UTC

Return-Path: <robert@raszuk.net>
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 D99C0130FCB for <idr@ietfa.amsl.com>; Mon, 11 Mar 2019 04:38:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=raszuk.net
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 94M7EgmhhPY3 for <idr@ietfa.amsl.com>; Mon, 11 Mar 2019 04:38:27 -0700 (PDT)
Received: from mail-qt1-x82a.google.com (mail-qt1-x82a.google.com [IPv6:2607:f8b0:4864:20::82a]) (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 5604B129AA0 for <idr@ietf.org>; Mon, 11 Mar 2019 04:38:27 -0700 (PDT)
Received: by mail-qt1-x82a.google.com with SMTP id z17so4562095qtn.4 for <idr@ietf.org>; Mon, 11 Mar 2019 04:38:27 -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 :cc; bh=afM0Nbf6LTsBoSwHKqiz4rdAN+Z9W8DZNT3fpvPmlGI=; b=GYuPcv/7y7JET85ek+IOXliz0vCuARP8n6r3CKS93aM5yW2djSqkc1MloSxrsBaz8W 0mb/1M85MxaB1+6gzGeg9k5Y2HxM1EHzhlkz+70AasWyVJdMR2aEcNvawj03q2ClIqlA np656334RmE0Duj4GIM9vVocv8ToqY4VkGfz8/YhB3/u3qMQMCXUSsYtZPWy0Odq7iBS rcno0Z1jeLYQExu/pkYtKPuLwWr2f5zGcesIRkoUaS+yVXQ1Or3i1f29MPB0P7rpi3tE GACTfNC1WJ+pmdGQmFIDgSpwBrkAyYQzDEgBSEcWPnG0WJGyJETQuQ05p+TGHQOtGBcT dkxw==
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=afM0Nbf6LTsBoSwHKqiz4rdAN+Z9W8DZNT3fpvPmlGI=; b=uem7l9qbrLLGUgh/Vpq5jgH7rHXr2AsmR3csGmGt6xv5FNjIh+67fTcDCUyvny3GvA SoFOpEF9GzedfnYEPlchQHnT+h20EFgnkJhLS73gDtPcwTLCmAFO8jNSnWnXa1DRbdL6 bzR/qZ03kSVii921MhhiWi8xmy76EbFKlfWbXliWaF5ORns3JDwKbwoXB6iHkFvq4EnW s2ac9SdlXaLEyKiD/B40V+1bl5eCPv6bPdfbw7b1wDsGY4pfdfiMULvVrJRL4hlYDdxF bjnyxS2mHKYvRdl38tUP8bwQkYLP2kHgVA5CockZTwKFrEQ7no0U9uyfo/L/SyacKBJ2 BPzA==
X-Gm-Message-State: APjAAAVsMgKFJ4WDV2Tfb6281UV46FOM3f6zCu6tlhXCrcdfrovxwL9g VpWAn5CZ5XyHJUjpKa6BaBp4irjylTXtXv32BMwhPw==
X-Google-Smtp-Source: APXvYqyAW7NMDQGt8m9G2MZ56my/DfCtu3JtLwWidQY1+OIY/WEbxHX/3MFQanc7gUDiQ1DCbhv6O1BrjyIlmn/7UGo=
X-Received: by 2002:ac8:6b92:: with SMTP id z18mr5845369qts.361.1552304306397; Mon, 11 Mar 2019 04:38:26 -0700 (PDT)
MIME-Version: 1.0
References: <CAOj+MMEH276xQscJDXaGCH3wmZZynkfP+TJD-Zxd06ZyfxU1YQ@mail.gmail.com> <SN6PR11MB284547928521AD7AABD3D6AFC1480@SN6PR11MB2845.namprd11.prod.outlook.com>
In-Reply-To: <SN6PR11MB284547928521AD7AABD3D6AFC1480@SN6PR11MB2845.namprd11.prod.outlook.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Mon, 11 Mar 2019 12:38:13 +0100
Message-ID: <CAOj+MMGZQOosfLus46QB9_h-2YeiDx4T-28=tpK2R7sLSmCHVA@mail.gmail.com>
To: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
Cc: "idr@ietf. org" <idr@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c43e150583d00287"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/R1NAN_ujxE5hmtEa2WitmH_iJa8>
Subject: Re: [Idr] BGP flooding and AS-PATH
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 11 Mar 2019 11:38:30 -0000

Hi Ketan,

I was not talking about TORs .. they will get all info just fine.

I was talking about same stage peers as they can have same AS number and
with eBGP there may be a bit of challenge to get BGP updates accepted
orignated by same level device.

And I was only waiting for you to mention allowas-in or as-overwrite knobs
;)

Can you reflect those options in the draft? Or at least in any other way
address this scenario ?

Kind regards,
R.

On Mon, Mar 11, 2019, 11:41 Ketan Talaulikar (ketant) <ketant@cisco.com>
wrote:

> Hi Robert,
>
>
>
> Please check inline below.
>
>
>
> *From:* Robert Raszuk <robert@raszuk.net>
> *Sent:* 11 March 2019 15:05
> *To:* Ketan Talaulikar (ketant) <ketant@cisco.com>
> *Cc:* idr@ietf. org <idr@ietf.org>
> *Subject:* BGP flooding and AS-PATH
>
>
>
> Dear authors of draft-ketant-idr-bgp-ls-bgp-only-fabric,
>
>
>
> I would like to ask for a small clarification on how in the quoted RFC7938
> design are you going to propagate topology information between peers
> configured with the same AS number ? Say between devices belonging to tier
> 1 stage or to a sets in tier 2 stages ?
>
>
>
> Do you assume that those switches just do not need to be aware of each
> other's presence say for TE purposes ?
>
> *[KT] This isn’t necessary in the use-cases where controller is doing the
> TE computations. E.g. a TOR can delegate end to end TE computation (from
> itself all the way over the DCI/WAN to a remote node) to the controller.*
>
>
>
> Specifically I am curious how are you going to accomplish it in the cases
> where no AS-PATH removing controller is involved as described here:
>
>
>
> "An internal software component on any of the BGP routers
>
> (e.g. TE module) can also receive the entire BGP network
>
> topology information from its local BGP process."
>
> *[KT] This is a different variant of the TE use-case where the TOR itself can do TE computation. In this case, you are correct about the topology flooding via the controller when using the ASN scheme in https://tools.ietf.org/html/rfc7938#section-5.2.1 <https://tools.ietf.org/html/rfc7938#section-5.2.1> . For this use-case, there are other options and designs though (incl private AS for unique assignment to TORs, allowAS-in, etc.) to make this possible.*
>
>
>
> *Thanks,*
>
> *Ketan*
>
>
>
> Thx a lot,
>
> R.
>
>
>