Re: [Idr] Adoption and IPR call for draft-wang-idr-vpn-prefix-orf-03.txt (8/16 to 8/30)

Gyan Mishra <hayabusagsm@gmail.com> Tue, 30 August 2022 06:56 UTC

Return-Path: <hayabusagsm@gmail.com>
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 5E2DCC14CF02 for <idr@ietfa.amsl.com>; Mon, 29 Aug 2022 23:56:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 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, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yCzC8IBsrzDm for <idr@ietfa.amsl.com>; Mon, 29 Aug 2022 23:56:45 -0700 (PDT)
Received: from mail-pg1-x52c.google.com (mail-pg1-x52c.google.com [IPv6:2607:f8b0:4864:20::52c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D354C1522A6 for <idr@ietf.org>; Mon, 29 Aug 2022 23:56:45 -0700 (PDT)
Received: by mail-pg1-x52c.google.com with SMTP id 69so8200912pgb.13 for <idr@ietf.org>; Mon, 29 Aug 2022 23:56:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc; bh=i1I3jMoVuzBPG55bkA/9anEWDZQkeLnqbEpj2nck8yg=; b=Ah4EQ7IZdUzmT9GlHeD+BrQJv1XI56Kb04ICl4RLyvpQfiBq20EpSAoBaw+smaRyny aF0y4rgbow2rJsVAMP5V6+83K7EZflZ97WDRQZVIp43IIr5jH63bSKrl2GM3yuVaKan1 ya2cTTbpF7bxJuAkCrXNXunRB8C59NVqZA3ZGb/q1TYUWNgt4jzkpAcoobiUm2/ZZV9z 1ujhSwN5MZj+KZDktKkMJzI4DqCm1ostsODk5+ugt+hUWH6P7aPa2itPrpDWLSPmjrFc 5oyj1GAX59nwCBNGU8+PoUMnDTPsk8O0td4kAJQQaaKuO3z3MAsOXhFHLWoc0WxksGVF WV8g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc; bh=i1I3jMoVuzBPG55bkA/9anEWDZQkeLnqbEpj2nck8yg=; b=UsFsh6lSiqDWiul8CxtnJqylGBgyH8OzL1ECJhS4qNFAczp6PfY+m03mXW+60+D2nu aZzn8u/KEoHiOivW+aV+aFFkKCoJNJYploBEwJOOauth+EHa18V3zFEFEsQ4XpH+thQA zJkl5JjvDB1DYyw7mX1dnP/6gu+7rISsrkMiqynDfwUp6s+feDhTc7cSkGtVxASBmnob iNSltS/OlDOL7KdDVFeHP6M7OI9FcVSeNy61/p3QmuosoBC6GXCkYyDauKXqMqXumziX 4x/6J3QLhJ4iYu0RNivC4WKgJO+32jtMRa3Ru+kYpPDgrTGs2JhWe6pOoFAB86d1/02T GBDg==
X-Gm-Message-State: ACgBeo1N2K7g6LBmTTRJA07ZdkNqejdoW6mAU7rPZvArDnsB3DY2PYDq OHxj3jt3st/UK0TRcBK9xmHKlJ6WC6PtFda7BDmJ2Uju
X-Google-Smtp-Source: AA6agR4IK8T6jZIt3QDRF1g0LFVQXD+ZuflQ03nWCYEXBHRU7slZwUseeUxqA6PymdJc39V6Q03lF2oLOLyPtaHtoEY=
X-Received: by 2002:a65:4d48:0:b0:421:5af6:9278 with SMTP id j8-20020a654d48000000b004215af69278mr17083506pgt.1.1661842604704; Mon, 29 Aug 2022 23:56:44 -0700 (PDT)
MIME-Version: 1.0
References: <tencent_3C3279A3B4DAF8DA03F446E7AAE799D8AA09@qq.com> <CAEfhRrz5aAJmy2Ye1gqss2d72nm78n4SfeowO-FU7i4Z6Zpb+A@mail.gmail.com> <0CD78D4C-672F-41AA-8E1B-98CD8A875D21@pfrc.org> <CAEfhRrxkuYMmfcdX=M9PG2mN+D5fCBF5bVxd1bSA2O9PU5G-gA@mail.gmail.com> <000001d8bbba$ceb9e4b0$6c2dae10$@tsinghua.org.cn> <CAEfhRrwrKJ4A=QQBWRXtLKi-U0udv+zPuWoW0wqbeMQ2U-=JXA@mail.gmail.com> <CABNhwV3=-rXCEsM1NJXt=ktQwAryBayZGjGbSqASEZ1ywomb8w@mail.gmail.com> <CAEfhRrxcfqr-WvW4ujtXhh8ToMjEBAtTqKMgULNUtdS7Xi3FfQ@mail.gmail.com> <CABNhwV02myvd_NBC6J9JFNuAURwhJ3o=JfE4=5G_az5N=WVJHQ@mail.gmail.com> <CAOj+MMHzv3Eykf7Wjk=oes2PiSXsTDTv6n+TvKeKMbF3bRpaKA@mail.gmail.com>
In-Reply-To: <CAOj+MMHzv3Eykf7Wjk=oes2PiSXsTDTv6n+TvKeKMbF3bRpaKA@mail.gmail.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Tue, 30 Aug 2022 02:56:32 -0400
Message-ID: <CABNhwV0cV06PodMbN2dDYmXQpKs_OGVEG-bENpVWDPo=fh5Z5w@mail.gmail.com>
To: Robert Raszuk <robert@raszuk.net>
Cc: Igor Malyushkin <gmalyushkin@gmail.com>, Sue Hares <shares@ndzh.com>, idr <idr@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000020493a05e76fe23a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/zFmIzrXxBrPrj71Kk65YlWFnxRg>
Subject: Re: [Idr] Adoption and IPR call for draft-wang-idr-vpn-prefix-orf-03.txt (8/16 to 8/30)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 30 Aug 2022 06:56:49 -0000

Hi Robert

You are mentioning RFC 5291 section 6 top of page 8 talks about
when-to-refresh immediate or deferred.



   If the When-to-refresh indicates IMMEDIATE, then after processing all
   the ORF entries carried in the message the speaker re-advertises to
   the peer routes from the Adj-RIB-Out associated with the peer that
   have the same AFI/SAFI as what is carried in the message, and taking
   into account all the ORF entries for that AFI/SAFI received from the
   peer.  The speaker MUST re-advertise all the routes that have been
   affected by the ORF entries carried in the message, but MAY also re-
   advertise the routes that have not been affected by the ORF entries
   carried in the message.

   If the When-to-refresh indicates DEFER, then after processing all the
   ORF entries carried in the message the speaker defers re-
   advertisement to the peer routes from the Adj-RIB-Out associated with
   the peer that have the same AFI/SAFI as what is carried in the
   message, and taking into account all the ORF entries received from
   the peer until the speaker receives a subsequent ROUTE-REFRESH
   message for the same AFI/SAFI either without any ORF entries, or with
   one or more ORF entries and When-to-refresh set to IMMEDIATE.


      We can add this caveat related to when to refresh to the draft.

Kind Regards

Gyan
On Mon, Aug 29, 2022 at 4:42 PM Robert Raszuk <robert@raszuk.net> wrote:

> Gyan,
>
>
>> I am not understanding this in quotes
>>
> “ but it is still receiving new routes from the RR (RR hasn`t received and
>> processed the ORF message).”
>>
>
> In addition to what Igor kindly already illustrated, let me also add a new
> dimension to this which apparently is not obvious.
>
> ORF action can be IMMEDIATE or DEFERED.
>
> When as in your examples from section 8 you set to IMMEDIATE then you get
> a full VPN table dump after each ORF msg. Yes filtered routes may not be
> there, but you will receive all eligible routes minus those in ORF message.
>
> And if you send second ORF entry with IMMEDIATE field it will be pending
> completion of the first table dump just to start another one and another
> ... Getting full table in BGP is always stressful to the BGP speaker
> especially here when number of VPN routes may exceed capacity od the node.
>
> On the other hand if you DEFER your routes which caused the issue in the
> first place will still be there for some time till you send ROUTE-REFRESH
> to said RR.
>
> Draft fails to discuss this aspect and indicate when and what type of ORF
> message will be sent.
>
> Thx,
> R.
>
>
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*



*M 301 502-1347*