Re: [Idr] WG LC on draft-ietf-idr-rpd-05.txt (7/15 to 7/29/2020)

Robert Raszuk <robert@raszuk.net> Mon, 27 July 2020 22:03 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 48E0B3A08C6 for <idr@ietfa.amsl.com>; Mon, 27 Jul 2020 15:03:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 xyI9EmfInzf1 for <idr@ietfa.amsl.com>; Mon, 27 Jul 2020 15:03:03 -0700 (PDT)
Received: from mail-ej1-x62e.google.com (mail-ej1-x62e.google.com [IPv6:2a00:1450:4864:20::62e]) (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 B05593A08C0 for <idr@ietf.org>; Mon, 27 Jul 2020 15:03:02 -0700 (PDT)
Received: by mail-ej1-x62e.google.com with SMTP id o18so18588950eje.7 for <idr@ietf.org>; Mon, 27 Jul 2020 15:03:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=W9LtdOOxE7bvUK9xoIIhnmJ6MnZLh55CFp+nXyQ2EmI=; b=YFXxbQ/85WjVRoUu6koUuzgne/uz7tQvw6ZLIeRWvIpXNnDldVvOfkgIAT1qds9I9w drSigL8lx0ShAfpyFQ32FQfNf/CAEUuNsDiLSjgV1rCM2w7VVT4VEmI31oI1uSfVlaTE lmgfgs12azqmr92awcK+yKcpEqw3afgf/+0rBrocNzDMybO/MdTKrhmQel8sPKTDzppF E+nhy7zlosbCzDtDcIk/879JNn7qgNEO4VDf0R7kjqo650THTveoYQ9CPBkGTXLB4jxh BMkB4RYWTGq3eOwTg3W8dAo66jgYxwZCh6vIvMl6Lj+AAqSoONJwpiaL/SN8j016KVoj CV5A==
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=W9LtdOOxE7bvUK9xoIIhnmJ6MnZLh55CFp+nXyQ2EmI=; b=raupPxtWld5ymOiG+DeRPOUOZP5F67pP5RNVmNCN00Ie9I08oIsOdYFwNJ01E7P6W7 Kd1HG0kynn9w6Kj167P6HY2E2uo5p11TVT28ulNzw7ihZahgM0GgG7XHRBw2bIdd+YPT IKNtcSgIHbK4EBgk9NVzvATVz6+DK2HiIurEOHTG+2H+MfpmKNUKJ1ca8P1cwJDDgXs+ Og1UKBJCWSyiCU2I1JGlNKGwyirh+LPPTZOlbF9LUx2sTj+8AI4XxZZqWlImHvhhuCZB 74kPdULqPi4TAuRA8/vD9/v9Jh4Pqf8hnwHvAFIYkTa/q6pj39tQLPZFBILd/GHqldM1 O6Hg==
X-Gm-Message-State: AOAM532Ydja6CUvyzKY3hiqzRp0sMfUc+2oddGfZsYRvbemTDaqisQRS SreVBGKvjIW+xgJXgAZleHA96rG28BUl1iEb2z65aEkSY5I=
X-Google-Smtp-Source: ABdhPJwwJJYdkwo6hMGqlDHQSSkhTxcRX/PzuKZn7SIZGeS6Cf8LZPOfxD5eX4ukiHwVQrv+v2NucHJuh6C0RlAxmpk=
X-Received: by 2002:a17:906:2490:: with SMTP id e16mr11375133ejb.386.1595887381127; Mon, 27 Jul 2020 15:03:01 -0700 (PDT)
MIME-Version: 1.0
References: <003701d65aa9$689a64d0$39cf2e70$@ndzh.com> <CAOj+MMGG6usHpQrn020LwWd7obt8PRPk9oii1drk0UPhyG5_gw@mail.gmail.com> <MW3PR11MB457041054724225FB0DEB25DC1760@MW3PR11MB4570.namprd11.prod.outlook.com> <MN2PR13MB3117CEF5726D2711D21C97BBF2720@MN2PR13MB3117.namprd13.prod.outlook.com>
In-Reply-To: <MN2PR13MB3117CEF5726D2711D21C97BBF2720@MN2PR13MB3117.namprd13.prod.outlook.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Tue, 28 Jul 2020 00:02:50 +0200
Message-ID: <CAOj+MMGZPi16FUSwn4N4q23RLhDtCmYbSjm6_P0K5OJ3KnZinQ@mail.gmail.com>
To: Huaimo Chen <huaimo.chen@futurewei.com>
Cc: "Ketan Talaulikar (ketant)" <ketant=40cisco.com@dmarc.ietf.org>, Susan Hares <shares@ndzh.com>, "idr@ietf. org" <idr@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007443e105ab737c71"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/EbfI5pCMMpZSTcxUjUCC1Sf1c70>
Subject: Re: [Idr] WG LC on draft-ietf-idr-rpd-05.txt (7/15 to 7/29/2020)
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, 27 Jul 2020 22:03:06 -0000

> [HC]: Yang model seems mainly used in relatively static or stable
configurations.

Well that's a problem with the "user" or bad habits not with the YANG model
itself.

Nothing stops to use config push as dynamically as required to network
elements.

Best,
Robert.


On Mon, Jul 27, 2020 at 10:57 PM Huaimo Chen <huaimo.chen@futurewei.com>
wrote:

> Hi Ketan,
>
>     Thanks much for your comments.
>     My answers/explanations are inline below with prefix [HC].
>
> >Some more/other comments on why I believe this draft is not a good idea:
>
>
>
>    - How does the controller or provisioning entity know the status of
>       the Route Policy provisioning on the target router. Even that it was
>       successfully propagated to it and installed on it?
>
> [HC]:  It seems that BGP protocols guarantees the BGP UPDATE with the
> route policy reaches the target router. When a BGP speaker as a controller
> sends a BGP UPDATE to a peer, there is no need for the ack from the peer
> about whether it is received, processed, and installed. The controller is
> monitoring the traffic of the network almost in real time, and adjusting
> the traffic dynamically almost in real time. The former gets the status of
> the network regarding to the traffic.
>
>
>    - Seems like one can have multiple policies advertised for a single
>       peer/neighbor? How would they be handled?
>
> [HC]: For multiple policies advertised to a single peer/neighbor, they are
> processed one by one by the peer/neighbor.
>
>
>    - The draft has support for IPv4 and IPv6 prefix list and AS regex.
>       What other route policy tools does the WG expect to extend in further
>       drafts? Perhaps we end up with yet another boatload of extension drafts for
>       BGP for RPD?
>
> [HC]: It seems that the current draft defines a small set of extensions (6
> sub TLVs), which is enough to support adjusting the traffic dynamically in
> the live networks. If there are some new requirements in the future, the
> extensions would be small too.
>
>
>
> We have Route Policy yang model defined at the IETF for provisioning of
> route policies that provide better and more comprehensive solution than the
> proposal in this document. That approach is also very robust from
> operational perspective. We don’t need to be putting this into BGP protocol.
>
> [HC]: Yang model seems mainly used in relatively static or stable
> configurations. For frequently changing route policies, the solution
> proposed in the draft is more suitable. It makes the operations and
> maintenance on the network simpler. For example, in one metro area network
> without using the solution in the draft, planning and implementing an
> adjustment/redirection of a service traffic takes days. After the solution
> in the draft is deployed in the network with a controller NCE, this takes
> just minutes instead of days.
>
>
> Best Regards,
> Huaimo
> ------------------------------
> *From:* Idr <idr-bounces@ietf.org> on behalf of Ketan Talaulikar (ketant)
> <ketant=40cisco.com@dmarc.ietf.org>
> *Sent:* Thursday, July 23, 2020 6:02 AM
> *To:* Robert Raszuk <robert@raszuk.net>et>; Susan Hares <shares@ndzh.com>
> *Cc:* idr@ietf. org <idr@ietf.org>
> *Subject:* Re: [Idr] WG LC on draft-ietf-idr-rpd-05.txt (7/15 to
> 7/29/2020)
>
>
> +1 and I also agree on Jakob’s comments/discussion on a parallel thread.
>
>
>
> The individual version of this draft was called draft-li-idr-flowspec-rpd.
> When it came up for WG adoption, perhaps most people thought it was yet
> another Flowspec extension and did not have a close look at it.
>
>
>
> The draft got adopted in Nov 2019 and since then, there has hardly been
> any change for it (other than IANA allocations update) :
> https://www.ietf.org/rfcdiff?url1=draft-ietf-idr-rpd-00&url2=draft-ietf-idr-rpd-05
> <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Frfcdiff%3Furl1%3Ddraft-ietf-idr-rpd-00%26url2%3Ddraft-ietf-idr-rpd-05&data=02%7C01%7Chuaimo.chen%40futurewei.com%7C28cc9cc452284af4ab3508d82eef9d08%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637310953981956964&sdata=vUgOeTbdLbvoAWIi17vzORiS8UxREO4JoanDDuuGodM%3D&reserved=0>
>
>
>
> I am not sure if this document has received sufficient review and inputs
> from the WG over the recent 9 months of its life as a WG document. Those
> provided by Robert previously seem not to have been incorporated?
>
>
>
> Not sure if I missed implementation reports or some operator feedback on
> this.
>
>
>
> Some more/other comments on why I believe this draft is not a good idea:
>
>
>
>    - How does the controller or provisioning entity know the status of
>    the Route Policy provisioning on the target router. Even that it was
>    successfully propagated to it and installed on it?
>    - Seems like one can have multiple policies advertised for a single
>    peer/neighbor? How would they be handled?
>    - The draft has support for IPv4 and IPv6 prefix list and AS regex.
>    What other route policy tools does the WG expect to extend in further
>    drafts? Perhaps we end up with yet another boatload of extension drafts for
>    BGP for RPD?
>
>
>
> We have Route Policy yang model defined at the IETF for provisioning of
> route policies that provide better and more comprehensive solution than the
> proposal in this document. That approach is also very robust from
> operational perspective. We don’t need to be putting this into BGP protocol.
>
>
>
> In summary, my suggestion would also be not proceed further on this
> document.
>
>
>
> Thanks,
>
> Ketan
>
>
>
> *From:* Idr <idr-bounces@ietf.org> *On Behalf Of *Robert Raszuk
> *Sent:* 17 July 2020 18:38
> *To:* Susan Hares <shares@ndzh.com>
> *Cc:* idr@ietf. org <idr@ietf.org>
> *Subject:* Re: [Idr] WG LC on draft-ietf-idr-rpd-05.txt (7/15 to
> 7/29/2020)
>
>
>
> Dear IDR WG,
>
>
>
> As discussed previously on the list I strongly object to proceed with this
> draft any further.
>
>
>
> While I am as others quite sceptical about distributing more configuration
> over BGP this can be said to be debatable especially for p2mp applications.
>
>
>
> However including peer's IP address in the NLRI to which given policy
> applies goes completely AGAINST BGP spray principle of p2mp
> information distribution. Adding such extension to BGP can only deteriorate
> the protocol further. It is not a fit in p2mp protocol to by definition use
> it as p2p transport channel.
>
>
>
> The prefix 0 which is in the draft is not the solution to the above
> problem.
>
>
>
> Moreover wide community ATOM also can already contain that peer's address
> so placing it in the NLRI of MP_REACH is not needed at all.
>
>
>
> To the specific questions asked:
>
>
>
> Ad 1) No.
>
> Ad 2) No.
>
> Ad 3) No..
>
> Ad 4) No.
>
> Ad 5) Yes.
>
>
>
> Kind regards,
>
> R.
>
>
>
>
>
> On Wed, Jul 15, 2020 at 3:11 PM Susan Hares <shares@ndzh.com> wrote:
>
> This begins a 2 week WG LC on draft-ietf-idr-rpd
>
> from 7/15 to 7/29/2020.  You can obtain this draft at:
>
> https://datatracker.ietf.org/doc/draft-ietf-idr-rpd/
> <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-idr-rpd%2F&data=02%7C01%7Chuaimo.chen%40futurewei.com%7C28cc9cc452284af4ab3508d82eef9d08%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637310953981966953&sdata=te9utkoi5bJl%2BT167KdWJQ%2BHYXaOaogxnvPQZLvbbWI%3D&reserved=0>
>
>
>
> This draft defines a new AFI/SAFI and new atoms
>
> for the Wide Communities.  This WG LC has been delayed
>
> as I waited for a resubmission of the Wide Communities draft.
>
> I had hoped to do these 2 WG LC in parallel.
>
>
>
> I’ve not received the Wide Communities draft, but we will
>
> start this WGLC to provide feedback to the authors.
>
> We may have to run a short follow-up to this WG LC
>
> If there are changes to the Wide Communities draft during
>
> Its WG LC.
>
>
>
> There is an IPR statement on this draft.
>
>
>
> In your responses please answer the following questions:
>
>
>
> 1) Do you feel this draft has an solution that is acceptable
>
>    With the IPR as a WG RFC?
>
>
>
> 2) Do you feel this draft is ready to publish?
>
>
>
> 3) Do you know of implementations of this draft?
>
>
>
> 4) Do you know of deployments of this draft?
>
> If so, is this feature useful in the deploy ments.
>
>
>
> 5) Do you feel that Wide Communities is ready for
>
> Publication?
>
>
>
> Cheerily, Susan Hares
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
> <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fidr&data=02%7C01%7Chuaimo.chen%40futurewei.com%7C28cc9cc452284af4ab3508d82eef9d08%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637310953981966953&sdata=uA9je9D95WX4sCUMQXWMpxWkKPo%2FbZY%2F1OiVNQKeggM%3D&reserved=0>
>
>