From nobody Wed Sep 30 15:29:07 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 B62213A0D03 for ; Wed, 30 Sep 2020 15:29:05 -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 bBOzZjsTOVOV for ; Wed, 30 Sep 2020 15:29:03 -0700 (PDT) Received: from mail-vs1-xe32.google.com (mail-vs1-xe32.google.com [IPv6:2607:f8b0:4864:20::e32]) (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 BD4E53A0D02 for ; Wed, 30 Sep 2020 15:29:03 -0700 (PDT) Received: by mail-vs1-xe32.google.com with SMTP id u7so1354330vsq.11 for ; Wed, 30 Sep 2020 15:29:03 -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=HBSJ4Ld72+xOV2v8YNHvro90nPDRRnNHqFStvQ1nMlY=; b=Ud5cGHr6thj3nbecvyurJLGsne7fNuLAc9uwp47+G9kC3PbfJHKbnTXiwIW4mf6l0O avD0OOaBg8D29p58AdZDDtoga3PAGiJ4ews4Utz0nm+qgr432OWkzFt3k/Xh1f8haXLA QyKF0EZzPOLOcXjVaKivPoIx8RZVD+dhYhMicAv+uWibm0eS7a7IeAPrb+fIBOkSYWRG M7IE1VH3GabR5i2bt3FVDjdgdODfrFUuRLdfbpz32rwwd1diiIGg5VFHN295GAutCs93 Qe3VSKFq78L8XvmYys0cgO2HIoq5/dE8+JVt9DV3HiMWwcEgkEHm/8EfCVYXUhAhjWMe Si0g== 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=HBSJ4Ld72+xOV2v8YNHvro90nPDRRnNHqFStvQ1nMlY=; b=IaabNoufunB2yMWTGBYqIiZJkHBY9cxKeeBFf7nHH0ptKZdGVJX5VHhLzQuVu0Rpbh AyT4iIC8OWLiiCN4zJcOx2jHw/eODxvIoPBhuxqc9aUMOPbVqH3drWqeUL8VUJl0VL7z +sbymT2kRRhd+XkpK1eHFIS1UJUGyUtT1Q8PeCzLa5JMJc0YLKmhWvoWgXE9F8Adqwps YEQ3K6ZqJmwvAYpCMLrVs2VwVLegK4w22ACUnO9QyNMzAIlst5jPWWaNwgeGOJ6yHbod JjXWXU6My4ZkzFgX0v0Vw6bFHTCSUyXDV8ROSKKMoqykJCbTxcEex6bWMNdKyGglu35S oPFA== X-Gm-Message-State: AOAM533p/9cL8IyaEVNiX7nW0Tq++LZMdaukiO93eHoD2dZmb8V4EYdp k3YdSYkV00LTTienwB44THW3bWBxKAF5zeEFODGgX6Ue35wWag== X-Google-Smtp-Source: ABdhPJzOI9RE97NjXY2dXu9wHCoVALUQ3fzSL1xxzePUl7h6TyafnV0n1XOzsl2L6sTbGQLReFtRbxFiyU40k1x/4jI= X-Received: by 2002:a67:e248:: with SMTP id w8mr3039287vse.33.1601504942659; Wed, 30 Sep 2020 15:29:02 -0700 (PDT) MIME-Version: 1.0 References: <160147241917.18722.10402627847451321205@ietfa.amsl.com> In-Reply-To: From: Gyan Mishra Date: Wed, 30 Sep 2020 18:28:51 -0400 Message-ID: To: Melchior Aelmans Cc: idr Content-Type: multipart/alternative; boundary="00000000000036a12705b08f6dd8" 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 22:29:06 -0000 --00000000000036a12705b08f6dd8 Content-Type: text/plain; charset="UTF-8" Hi Melchior Thanks for the quick response! For both inbound and outbound direction we have today the option to set prefix limit and threshold for the peer disconnect scenario, so now we would add a 3rd parameter is your suggestion. I agree and that makes sense. With this option when the limit hits and we are clipping over the limit it would be possible to also do the warning flag with it so we are logging when clipping and maybe even number of routes clipped in the log message. If you have a GitHub for the draft I would be happy to co-author the draft and provide any additional feedback. Kind Regards Gyan On Wed, Sep 30, 2020 at 12:27 PM Melchior Aelmans wrote: > Hi Gyan, > > Thanks for the feedback! > Good point and agreed this could be useful. Would you be okay with having > this as an additional action next to shutdown? > > Cheers, > Melchior > > On Wed, Sep 30, 2020 at 4:53 PM Gyan Mishra wrote: > >> 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 >> >> >> >> >> > > -- *Gyan Mishra* *Network Solutions A**rchitect * *M 301 502-134713101 Columbia Pike *Silver Spring, MD --00000000000036a12705b08f6dd8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Hi Melchior

Thanks for the quick response!
=
For both inbound and outbound direction we have= today the option to set prefix limit and threshold for the peer disconnect= scenario, so now we would add a 3rd parameter is your suggestion. =C2=A0

I agree and that makes se= nse.=C2=A0 With this option when the limit hits and we are clipping over th= e limit it would be possible to also do the warning flag with it so we are = logging when clipping and maybe even number of routes clipped in the log me= ssage.

If you have a Git= Hub for the draft I would be happy to co-author the draft and provide any a= dditional feedback. =C2=A0

Kind Regards=C2=A0

Gyan
On Wed, Sep 30, 2020 at 12:27 PM Melchior Aelmans &= lt;melchior@aelmans.eu> wrote= :
Hi Gyan,

Thanks for the feedback!=C2=A0
Good point and agreed thi= s could be useful. Would you be okay with having this as an additional acti= on next to shutdown?

Cheers,
Melchior

On Wed, Sep 30, 2020 at 4:53 PM Gyan Mishra <hayabusagsm@gmail.com> wrote:


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

As suggested in earlier WG meetings (both in GROW and I= DR) we have split the Maximum Prefix Limits draft=C2=A0int= o=C2=A0Maximum Prefix Limits Outbound=C2=A0and=C2= =A0Maximum Prefix Limits Inbound.
The au= thors are looking for your feedback and input on both.

=
Thanks,
Melchior

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





A Ne= w Internet-Draft is available from the on-line Internet-Drafts directories.=








=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: Revised BGP Maximum Prefix Limits Outb= ound


=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 Stucch= i


=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-outbou= nd-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-09-30





Abst= ract:


=C2=A0 =C2=A0This document updates RFC4271 by adding a con= trol 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 Protocol (BGP)


=C2=A0 =C2= =A0implementations.











The IETF= datatracker status page for this draft is:


https://datatracker.ietf.org/doc/draft-sas-idr-maxpref= ix-outbound/





There are also htmlized versions av= ailable 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 submissi= on


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





Internet-Drafts are also available by anony= mous 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-announc= e


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


or ftp://ftp.ietf.org/ietf/1shadow-s= ites.txt




___________________= ____________________________

Idr mailing list

Idr@ietf.org

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

--

Gyan Mishra

Network Solutions Architect=C2=A0

M 301= 502-1347
13101 Columbia Pike=C2=A0
Silver Spring, MD






--


Gyan Mishra

= Network Solutions Architect=C2=A0

M 301 502-13= 47
13101 Columbia Pike=C2=A0
Silver Spring, MD


--00000000000036a12705b08f6dd8--