Re: [Idr] BGP Auto-Discovery Protocol State Requirements

Robert Raszuk <> Fri, 19 March 2021 14:22 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0EA613A1654 for <>; Fri, 19 Mar 2021 07:22:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Status: No, score=-2.097 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] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id U7WZJqdObyxC for <>; Fri, 19 Mar 2021 07:22:18 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::12c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 91D3E3A1401 for <>; Fri, 19 Mar 2021 07:22:18 -0700 (PDT)
Received: by with SMTP id q13so10268248lfu.8 for <>; Fri, 19 Mar 2021 07:22:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=qyz4WgbhxQvSGbAYS8JIf1awU0IsejoRFVmmQSby+e0=; b=JTJhonzMBI8O5DEmO2WoN/PrkRlLQrPQEZbawr05c46CYRRI+IZP1BApzUSfm1utbM 8CYWB5NqyyOZm7lWHdCbkezg8mjhNNgkVG31nClPZibem61NHT+1lYtNiqV/NKXSukVh 1wV86ZPzHeFUkr0WC2+i2AhGgmS/UzuP8ol/p99vi4vIsRb4xDCYJecCzwEu2aMw90Fi V6EsV0ELzLuiUZUoN3FakklEb3ftJCL0YtEQF3vD0HLHItlrsJpdnJWdOEaTntIXCPHM X8dbHnyHjUBw/ADywjwQVeMWx4vICqSZ52hfp1YI4kEpy2eHniG7WjS8TzJ77WGGlFC2 xG4Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=qyz4WgbhxQvSGbAYS8JIf1awU0IsejoRFVmmQSby+e0=; b=dkLUGIasShc9tXiscCkEMrBSbTsbUJEvDshvFKk8fzfUVFdaqXy3WohBUkGXrS4EMe yuHXQBM+LonxrMkdieEg5Hqb8wr54HfafBGkFQuJPQeaIGMhLT/t8k7b3fUgEdj5EIZl 48EUtk2WH9UtYZMwQaGR5QUxkA8Gzigk9lcsRE/qkWhmrP1RtZWiXwrN5lbY5HGn7Ga9 y2T4FN80c+diiAPieowYHvEVn/tRIBQ8Xh0UxPGo7vciyydDXFpnDsEE15umPImddZud p/cAGoLFGH2Zn7Xv97ux6TPMhMq496Nri6i55hy6O73qjTs/2dw0yXiLxB0PM0BW61eB H6iw==
X-Gm-Message-State: AOAM532NShRmiaKtOmFLjFkdXNwA15p0IUiHWW8E5lGXqyMcKg6MWYZa 5TR8DfnkDJSONH6icDmPpxxwsYvgEIo92IRdZq73YQ==
X-Google-Smtp-Source: ABdhPJzxjDATJpo8fltRY5WT0OKG2QdNWMfySUJiT4xitFY9u4aG3X9agx++PxsGbhfB091ftIfSVObUjtCMXnEcQAE=
X-Received: by 2002:a19:712:: with SMTP id 18mr937561lfh.591.1616163735979; Fri, 19 Mar 2021 07:22:15 -0700 (PDT)
MIME-Version: 1.0
References: <> <> <> <> <> <> <>
In-Reply-To: <>
From: Robert Raszuk <>
Date: Fri, 19 Mar 2021 15:22:05 +0100
Message-ID: <>
To: Jeffrey Haas <>
Cc: Tony Przygienda <>, "" <>, "Acee Lindem (acee)" <>
Content-Type: multipart/alternative; boundary="00000000000061df0b05bde47140"
Archived-At: <>
Subject: Re: [Idr] BGP Auto-Discovery Protocol State Requirements
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 19 Mar 2021 14:22:20 -0000

> As noted at the beginning of this thread, you may not be able to get your
> SYN+ACK if you don't agree on security mechanisms or GTSM.  So, you need
> that state either in your discovery mechanism, or your provisioning.

You keep bringing GTSM here.

Aren't both DC nodes we are to establish a BGP session between under the
very same administration ? I don't get the need to put this in
auto discovery if we are sticking to the scope.

Even if we talk about Compute to TOR .. for one this is still under same
admin. And it is actually a security feature not to add this to auto
discovery as this info can be passed out of band to what value to set
your TTL such that TOR answers.