IETF Logo Mail Archive

[Idr] Multi Instance BGP

Robert Raszuk <robert@raszuk.net> Mon, 22 October 2018 21:11 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 809C7130F18 for <idr@ietfa.amsl.com>; Mon, 22 Oct 2018 14:11:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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] 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 Y4jBN9Alf-D9 for <idr@ietfa.amsl.com>; Mon, 22 Oct 2018 14:11:39 -0700 (PDT)
Received: from mail-qt1-x82b.google.com (mail-qt1-x82b.google.com [IPv6:2607:f8b0:4864:20::82b]) (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 7F71A130E99 for <idr@ietf.org>; Mon, 22 Oct 2018 14:11:38 -0700 (PDT)
Received: by mail-qt1-x82b.google.com with SMTP id d14-v6so48133588qto.4 for <idr@ietf.org>; Mon, 22 Oct 2018 14:11:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; h=mime-version:from:date:message-id:subject:to; bh=qha/6sCdaojLEvvGn/XTmfpYr7l9+Th0DG1N3h/Dhh8=; b=aVC3XwltDpCl/VDDOWtuwv+nD+7wzKWC65szcIm5I9991Ad/5eteBPBAaYcMMTkW+Z 0l012vibcbd4GTFHxVGoEdYsWBYCFxPBeUk5NoyO0efIpTMmCCWPl8o7/WJr7dOAIKpm tX6VBK3FiTOc9ZIDQ3C0iL56D+0Uvd0Ij1BQSGxwTaE/SRK4jUqUjGWetehzWnTk4zwx L8dZsBxrg3Fu8yQtXka0gn6oR7fivM/FP8bBUmCHDQCHU6ZMieLuxJrLJi8/UC30y2a7 cK4MY+9AI7iJTuq4ISI6PO2/e45P4vZw/B2yGPNafwqqCdj1+WEtIcGaPTj/YEsLHJu8 PPiA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=qha/6sCdaojLEvvGn/XTmfpYr7l9+Th0DG1N3h/Dhh8=; b=AM8V3raiHAm3XkZ9kaNTOf4fCoAoue8UH9gZhFdqKeDWGWEiUSaMvHw1QeSlrQdxs0 +BY6C6p+mm9bW+u5BwAD0HIBg0heVFR4yIFSOmlPbVJIytBXF2q2ADzPtIVNoNRE2Hdx E0BAoZCeqY9Zh5FT5c91KnJQ6mbvFyj7cq3MNfhNrbvhM7JfUUlULuQtsjmCNB+E9vKJ kPIyLKUmS04aH2ibdLNGMeJP7gmXPwH8IknH1x7s1vpgBnhvJEBujc9MI1TPPDnR7gpD EDTCXO/SFypFPcdyu9lGo+FMzs2vQgXbWMkm9o1WD4utW79OkDPkKD7eynhR+SS9yBSj kGMA==
X-Gm-Message-State: AGRZ1gIttWi1Y9QJjsCDsa9SM+XijIHiKhRyVQpEp/wWA4txbV1FR84L QbbvCh34aLVZYnTOlUU/ZP+kG+d/H03+RBcGoKtc365o
X-Google-Smtp-Source: AJdET5cxyq8vaFxB5UdIne3wdHKZ4feSGCcXQuWa4af4At5lIC9SPmLY0NhI/wos3HYCCr2jGhSHoEzxeHFaLFCvCL4=
X-Received: by 2002:a0c:ea82:: with SMTP id d2mr5745298qvp.124.1540242697435; Mon, 22 Oct 2018 14:11:37 -0700 (PDT)
MIME-Version: 1.0
From: Robert Raszuk <robert@raszuk.net>
Date: Mon, 22 Oct 2018 23:11:27 +0200
Message-ID: <CAOj+MMHehQrkDDcnd5kAhq4AgdW-DbFErUMxRGffBo1P=1vYeg@mail.gmail.com>
To: idr@ietf.org
Content-Type: multipart/alternative; boundary="000000000000d95df50578d7b2fa"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/TWleKqy-zgCprZdew1no7AbedXs>
Subject: [Idr] Multi Instance BGP
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, 22 Oct 2018 21:11:53 -0000

Hello,

To meet the submission deadline I uploaded a below proposal for Multi
Instance BGP.

Please do not hesitate to provide any comments on or off the list.

I consider it as first possible step to separate BGP-LS (or for that matter
other non
routing related data) into independent BGP process primarily targeting to
run
on the x86 general compute hardware without making any changes to BGP code
therefor making it 100% backwards compatible.

If there is need we could discuss it during the interim meeting, otherwise
we could
just keep it for the list based comments.

Kind regards,
Robert

---------- Forwarded message ---------
From: <internet-drafts@ietf.org>
Date: Mon, Oct 22, 2018 at 11:00 PM
Subject: New Version Notification for draft-raszuk-mi-bgp-00.txt

A new version of I-D, draft-raszuk-mi-bgp-00.txt
has been successfully submitted by Robert Raszuk and posted to the
IETF repository.

Name:           draft-raszuk-mi-bgp
Revision:       00
Title:          Multi Instance BGP
Document date:  2018-10-22
Group:          Individual Submission
Pages:          9
URL:
https://www.ietf.org/internet-drafts/draft-raszuk-mi-bgp-00.txt
Status:         https://datatracker.ietf.org/doc/draft-raszuk-mi-bgp/
Htmlized:       https://tools.ietf.org/html/draft-raszuk-mi-bgp-00
Htmlized:       https://datatracker.ietf.org/doc/html/draft-raszuk-mi-bgp


Abstract:
   As the number of operational use cases of BGP grows there is demand
   to increase the level of separation and processing independence
   between various address families carried by BGP today.  This document
   augments base BGP specification in allowing local configuration of
   BGP port number by the operator to run parallel fully disjoined BGP
   instances allowing full processing separation between them.

   While local BGP implementation may already assure BGP process or
   thread robustnes the general aim here is to allow similar level of
   groups of BGP address families independence when running BGP code on
   general purpose hardware as well as x86 based route reflectors.

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

v2.23.0 | Report a Bug | By Email