From nobody Wed Sep 30 07:53:09 2020 Return-Path: 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 7694B3A0BF3 for ; Wed, 30 Sep 2020 07:53:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.087 X-Spam-Level: X-Spam-Status: No, score=-2.087 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 1iZq-TSgYQUJ for ; Wed, 30 Sep 2020 07:53:00 -0700 (PDT) Received: from mail-vk1-xa2c.google.com (mail-vk1-xa2c.google.com [IPv6:2607:f8b0:4864:20::a2c]) (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 98BA63A0B36 for ; Wed, 30 Sep 2020 07:53:00 -0700 (PDT) Received: by mail-vk1-xa2c.google.com with SMTP id n7so441236vkq.5 for ; Wed, 30 Sep 2020 07:53:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=F5JpiyoW+alf01GqYw5RtXf7L5XyDot7qjVwm/gnbvk=; b=Uq0vTpbSQebdMP7VIulCmBpLwwKhroat8/kpyu8hyjiDaNCSTWslWBEl0aPbfD+kJp fYrolX/ScM55ETSXjuAi3aTsRzcZImSTGiqupnBQls9lXhH17spFqAvYviNhTTIpF0vP KBlvJL7bAjm9cmufN2lnriLfHpEGq8nUXtZ8f0IBXi0pkasi4c6qYVe/F4bcbmLyyRrC O1k0HKRroexHNbQg4uoOIGZgHhkvEPFsLcpPEze+q9v1RTiVixaKZPcieTSpVKe+apxt MGSNn/dPnmUMSC7OyQyUNrfeomVF/dp4pisMw6VE9Juet7s48NnofhtzxeMoP8bZi8L8 u0DQ== 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=F5JpiyoW+alf01GqYw5RtXf7L5XyDot7qjVwm/gnbvk=; b=CU2knmRTfhWS8wQsg62WnTCh5jwk2qjYM2x0dmG6KcMEm+4xmkzFoaEkvNUjpvTGhv PZ6GEaCl0KSsna4iMxU4EBWWI5dwDjXAqLSk5aSgTpjJuW2tbpeLJsBevtgmge+eEwq8 G+8DMjiBfQur5MZmATlnt9rIoE6TlJ0UAY+iQekXUuOlVvGqy5QEPuLDlCCM/q+JPxkH y1FftVKgurR6mFVNETW7R+yQAfWoWylNpBdwwEdYKcU2n96h80MOzUzaUZF3wgVozt7f B/Um6RLfH834idcv6vHAVjHrQfXWwq4rgR81rUL1JGkuWgUPWrAS86fCLvZeGSj8LZnE X6sQ== X-Gm-Message-State: AOAM532VfbaYZ7egSYt8lS/R6/T+xaFyeEJ83vx9JXw9+UJu3n/xLxZW 2bVDiijHXBwngQ4YwoPXZJTU6OVHPBUnErfuLSYZH2OTnW135w== X-Google-Smtp-Source: ABdhPJxAv3TQyOp0jM/sJjO2BLnEZYtgJlKwhDHzrzyoDeuvCQwU2DbyvCkh74NKzyh85QJjyPMi3PWgAFORKTFXaHc= X-Received: by 2002:a1f:bf53:: with SMTP id p80mr1648006vkf.5.1601477579196; Wed, 30 Sep 2020 07:52:59 -0700 (PDT) MIME-Version: 1.0 References: <160147241917.18722.10402627847451321205@ietfa.amsl.com> In-Reply-To: From: Gyan Mishra Date: Wed, 30 Sep 2020 10:52:48 -0400 Message-ID: To: Melchior Aelmans Cc: idr Content-Type: multipart/alternative; boundary="000000000000394c7b05b0890e52" Archived-At: Subject: Re: [Idr] Fwd: I-D Action: draft-sas-idr-maxprefix-outbound-00.txt X-BeenThere: idr@ietf.org 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: Wed, 30 Sep 2020 14:53:08 -0000 --000000000000394c7b05b0890e52 Content-Type: text/plain; charset="UTF-8" Hi Authors Would it be possible to modify the action so that we have the option to not disconnect the peer and allow the peer to remain UP state but clip the routes above the upper limit and provide this option for both inbound and outbound directions. This was the PE resources are not impacted as well as the customer peer still remains in an Up state. Thanks Gyan On Wed, Sep 30, 2020 at 9:34 AM Melchior Aelmans wrote: > Hi IDR, > > As suggested in earlier WG meetings (both in GROW and IDR) we have split > the Maximum Prefix Limits draft > into Maximum > Prefix Limits Outbound > and Maximum > Prefix Limits Inbound > . > The authors are looking for your feedback and input on both. > > Thanks, > Melchior > > ---------- Forwarded message --------- > From: > Date: Wed, Sep 30, 2020 at 3:27 PM > Subject: I-D Action: draft-sas-idr-maxprefix-outbound-00.txt > To: > > > > > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > > > > > > > > > Title : Revised BGP Maximum Prefix Limits Outbound > > > Authors : Melchior Aelmans > > > Massimiliano Stucchi > > > Job Snijders > > > Filename : draft-sas-idr-maxprefix-outbound-00.txt > > > Pages : 9 > > > Date : 2020-09-30 > > > > > > Abstract: > > > This document updates RFC4271 by adding a control mechanism which > > > limits the negative impact of outbound route leaks (RFC7908) in order > > > to prevent resource exhaustion in Border Gateway Protocol (BGP) > > > implementations. > > > > > > > > > > > > The IETF datatracker status page for this draft is: > > > https://datatracker.ietf.org/doc/draft-sas-idr-maxprefix-outbound/ > > > > > > There are also htmlized versions available at: > > > https://tools.ietf.org/html/draft-sas-idr-maxprefix-outbound-00 > > > https://datatracker.ietf.org/doc/html/draft-sas-idr-maxprefix-outbound-00 > > > > > > > > > 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. > > > > > > Internet-Drafts are also available by anonymous FTP at: > > > ftp://ftp.ietf.org/internet-drafts/ > > > > > > > > > _______________________________________________ > > > I-D-Announce mailing list > > > I-D-Announce@ietf.org > > > https://www.ietf.org/mailman/listinfo/i-d-announce > > > Internet-Draft directories: http://www.ietf.org/shadow.html > > > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > > > _______________________________________________ > > Idr mailing list > > Idr@ietf.org > > https://www.ietf.org/mailman/listinfo/idr > > -- *Gyan Mishra* *Network Solutions A**rchitect * *M 301 502-134713101 Columbia Pike *Silver Spring, MD --000000000000394c7b05b0890e52 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Authors=C2=A0


Would it be possible to modify the a= ction so that we have the option to not disconnect the peer and allow the p= eer to remain UP state but clip the routes above the upper limit and provid= e this option for both inbound and outbound directions.=C2=A0 This was the = PE resources are not impacted as well as the customer peer still remains in= an Up state. =C2=A0=C2=A0

Thanks=C2=A0

Gyan

On Wed, Sep 30, 2020 at 9:34 AM Melchior Aelmans <melchior@aelmans.eu> wrote:
Hi IDR,

As suggested in earlier = WG meetings (both in GROW and IDR) we have split the Maximum P= refix Limits draft=C2=A0into=C2=A0Maximum Prefix = Limits Outbound=C2=A0and=C2=A0Maximum Prefix Limit= s Inbound.
The authors are looking for your feedback and inpu= t on both.

Thanks,
Melchior

---= ------- Forwarded message ---------
From: <internet-drafts@ietf= .org>
Date: Wed, Sep 30, 2020 at 3:27 PM
Subject: I-D A= ction: draft-sas-idr-maxprefix-outbound-00.txt
To: <i-d-announce@ietf.org>





A New Internet-Draft is available from the on-li= ne Internet-Drafts directories.








=C2=A0 = =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: Revise= d BGP Maximum Prefix Limits Outbound


=C2=A0 =C2=A0 =C2=A0 =C2=A0= Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: Melchior Aelmans


=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 Massimiliano Stucchi


=C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Job Snijders=


=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0= : draft-sas-idr-maxprefix-outbound-00.txt


=C2=A0 =C2=A0 =C2=A0 = =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: 9


=C2=A0 = =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : 2020-0= 9-30





Abstract:


=C2=A0 =C2=A0This document= updates RFC4271 by adding a control mechanism which


=C2=A0 =C2= =A0limits the negative impact of outbound route leaks (RFC7908) in order

=C2=A0 =C2=A0to prevent resource exhaustion in Border Gateway Prot= ocol (BGP)


=C2=A0 =C2=A0implementations.





=





The IETF datatracker status page for this draft is:=


https://datatracker.ie= tf.org/doc/draft-sas-idr-maxprefix-outbound/





The= re are also htmlized versions available at:


https://tools.ietf.org/html/draft-sas-idr-maxprefix-outbo= und-00


https= ://datatracker.ietf.org/doc/html/draft-sas-idr-maxprefix-outbound-00







Please note that it may take a couple of m= inutes from the time of submission


until the htmlized version an= d diff are available at tools.ietf.org.





Internet-Dra= fts are also available by anonymous FTP at:


ftp://ftp.= ietf.org/internet-drafts/








__________= _____________________________________


I-D-Announce mailing list<= br>

I-D-A= nnounce@ietf.org


https://www.ietf.o= rg/mailman/listinfo/i-d-announce


Internet-Draft directories:= http://www.ietf.org/shadow.html


or ft= p://ftp.ietf.org/ietf/1shadow-sites.txt




_______________________________________________

Idr mail= ing list

Idr@ietf.= org

https://www.ietf.org/mailman/listinfo/idr

--
--000000000000394c7b05b0890e52--