[GROW] Request for input on Prefix Limits by IETF 113 IDR session (3/4 to 3/25)
Susan Hares <shares@ndzh.com> Thu, 03 March 2022 17:53 UTC
Return-Path: <shares@ndzh.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id 17F323A1159;
Thu, 3 Mar 2022 09:53:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.061
X-Spam-Level:
X-Spam-Status: No, score=-4.061 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001,
RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_NONE=0.001,
T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001]
autolearn=ham autolearn_force=no
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 keOibd1DJTdK; Thu, 3 Mar 2022 09:53:14 -0800 (PST)
Received: from hickoryhill-consulting.com
(50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97])
(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 8569F3A10AD;
Thu, 3 Mar 2022 09:53:09 -0800 (PST)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS))
x-ip-name=50.107.120.176;
From: "Susan Hares" <shares@ndzh.com>
To: "'GROW WG'" <grow@ietf.org>
Cc: <idr@ietf.org>
Date: Thu, 3 Mar 2022 12:53:06 -0500
Message-ID: <01bc01d82f27$89b1a3a0$9d14eae0$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_01BD_01D82EFD.A0DD4950"
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
Thread-Index: AdgvJ03n0yJ1dLCmShmSdHv3I5nVjg==
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/zmCc9wiLOOJSYmNo5j2L7VyztpQ>
Subject: [GROW] Request for input on Prefix Limits by IETF 113 IDR session
(3/4 to 3/25)
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>,
<mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>,
<mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Mar 2022 17:53:24 -0000
Grow:
In the past you requested the IDR WG to consider drafts on prefix limits.
Two drafts proposed included discussions on prefix limits
(draft-wang-idr-vpn-prefix-orf-02.txt,
draft-sas-idr-maxprefix-inbound-04.txt)
Would you query the grow working group regarding:
a) hard prefix limits per BGP peer
a) (protocol enforced) maximum prefix (inbound)
b) (software enforced) maximum prefix (inbound)
c) (software enforced) maximum prefix (outbound)
b) thresholds prior to hard limits per BGP peer
c) What limits should be placed on VPNs?
What granularity
Do you think you could get an answer for IDR by
the end of IETF 113?
If you wish, I can also present the request at Grow at IETF 113.
5 minutes (what I need + why)
10 discussion (when I listen to operations experts)
Sue Hares
(idr co-chair)
--------------------
Drafts mentioned
Draft 1: draft-wang-idr-vpn-prefix-orf-02.txt
https://datatracker.ietf.org/doc/draft-wang-idr-vpn-prefix-orf/
Note: ORF mechanism not approved, but prefix limits discussion is useful:
https://mailarchive.ietf.org/arch/msg/idr/Lt5IQVUNPxhEh8-xvRTDIJZ24Kk/
New definitions: Weak-PE, rogue-PE
Draft 2: draft-sas-idr-maxprefix-inbound-04.txt
https://datatracker.ietf.org/doc/draft-sas-idr-maxprefix-inbound/
(in IPR call prior to adoption)