[Idr] draft-uttaro-idr-bgp-persistence
Robert Raszuk <robert@raszuk.net> Mon, 29 July 2019 08:07 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 844A712009C for <idr@ietfa.amsl.com>; Mon, 29 Jul 2019 01:07:52 -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_HELO_NONE=0.001, 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 kvFv86-Jnsjk for <idr@ietfa.amsl.com>; Mon, 29 Jul 2019 01:07:51 -0700 (PDT)
Received: from mail-qk1-x72a.google.com (mail-qk1-x72a.google.com [IPv6:2607:f8b0:4864:20::72a]) (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 CFC5A12008C for <idr@ietf.org>; Mon, 29 Jul 2019 01:07:50 -0700 (PDT)
Received: by mail-qk1-x72a.google.com with SMTP id s145so43498719qke.7 for <idr@ietf.org>; Mon, 29 Jul 2019 01:07:50 -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=+JhCTLOossFKhk8eoHBxXTtrKfuBYnmGjOZplF3s7aY=; b=UL4iZBTikjLNFHFiPcGaICtnlcrLbrVjH8K3BLiHkc+5p13rv8hgOZ2ZUJGel9hyuf mdpsZnPTDzwgtfHZEw5q+uFbSs6dEUjvZZMmNXU9b4xWmZgpLGmOMDNVR2gPEWf9Zdng n5YmR5bPSfyk4l10ZPali4xgcIi9UbZKbJGcThUWjnGu9g/Gf6hNz/tj9FmYEtysuCpE RgIf0/RloVJtL+MhrICVIXgD4d1Ny4A2fwCdxODGrWpV10zSd0QWRBR+XTUXHNOjhHoJ LXL/jNxBLvRmlc09YBaZEqf9khyhB8Yweoi2XvUV76G6c/c5c+cHKtBWer2Sp5VImhOq vsxA==
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=+JhCTLOossFKhk8eoHBxXTtrKfuBYnmGjOZplF3s7aY=; b=S0YZvE1RVLtVI1eXFxsRqKJNQfReJE5qlSFx3jYO+OhJbZo2kWxiGaeNMRncjXTOrz xJ65cT6uAtSwPH02utlpKFy4JKRP9/shmG+Iq61GzhGy+kTbIRyTpSYDoCsVZCu/7sE2 SXU05yIwyanSpAwgVaWlx+47tkW6SCZT1wE/yWF+tVtrOstyIMKyfyHe6vepVlSPXpUx 75gYy/2ER3nL/+A+C5dGcmv5TkgYvUESUtt4TEfEcyUzVv/AZTDiVXVsk2aalPS5EzT6 wGWiQ+YHo/Pty7uRtNBkKzb/3iyep7JwYHCbA6ElCS+RfTHjqUiiV/V/3g4VFA6YQZW1 KVQw==
X-Gm-Message-State: APjAAAXVe9b1vsTj/9ZtktNBBe7GU+pCo8fxKrBYE9R7jpGXDTj2RWAp 7w9wdJUJQogOTONiLq8y0ZxnakVwvPIZWIog5GMXZMsS
X-Google-Smtp-Source: APXvYqzA8Ft48tdPmyXGoPWF7TBUpDXQJ/iKte6+7IOPm1HcVdBe/hiMVH9Xbi4H3PK9lcw72RS6b5zSl00YeoNnLq0=
X-Received: by 2002:ae9:e411:: with SMTP id q17mr68917542qkc.465.1564387669661; Mon, 29 Jul 2019 01:07:49 -0700 (PDT)
MIME-Version: 1.0
From: Robert Raszuk <robert@raszuk.net>
Date: Mon, 29 Jul 2019 10:07:38 +0200
Message-ID: <CAOj+MME=scL9h7d9Jbh_3vYch6dTruTpseGLXx=peLwexEwH0Q@mail.gmail.com>
To: "idr@ietf. org" <idr@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000577037058ecd6308"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/yMXnPPAO-ALqDLqSQHaVw7PkDlM>
Subject: [Idr] draft-uttaro-idr-bgp-persistence
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, 29 Jul 2019 08:07:53 -0000
Hi, Assume LLGR has been negotiated and routes have been exchanged with LLGR community. The retention timer is looong. While I am happy to see that suggestions to follow GR procedures have been used the draft is pretty silent on one very important aspect - clearing persistent routes. GR procedures which rely on using GR time for it do not apply. Imagine I want to bring such session down and I do want to remove all routes including those marked as LLGR. How do I do that ? >From current draft the only way seems to be to reestablish a session with LLGR capability and readvertise subject routes with NO-LLGR community hoping it will clear the former routes. But even here we are at the mercy of local policy as per section 3.2 & 3.3 In any case that is pretty awkward method. Then we just had a little thread regarding max prefix in GROW WG. New draft there actually relies on BGP NOTIFICATION MSG with CEASE error code to remove all routes making on purpose crossing a max prefix limit a drastic event (of course unless warning only is set). Bottom line BGP here is used again as configuration tool not as dynamic routing protocol. I do not think this type of use of BGP which should be endorsed. If this proposal moves fwd it should clearly spell how not only to retain the LLGR eligible prefixes but also how to cleanly remove them when needed - way before they expire. Kind regards, R.
- [Idr] draft-uttaro-idr-bgp-persistence Robert Raszuk
- Re: [Idr] draft-uttaro-idr-bgp-persistence bruno.decraene
- Re: [Idr] draft-uttaro-idr-bgp-persistence Jakob Heitz (jheitz)
- Re: [Idr] draft-uttaro-idr-bgp-persistence Robert Raszuk
- Re: [Idr] draft-uttaro-idr-bgp-persistence bruno.decraene