Re: [Idr] I-D Action: draft-ietf-idr-rpd-05.txt

Gyan Mishra <hayabusagsm@gmail.com> Wed, 01 July 2020 04:30 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 8CA1F3A0C6A for <idr@ietfa.amsl.com>; Tue, 30 Jun 2020 21:30:59 -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 0E_9Nn_Q9GQg for <idr@ietfa.amsl.com>; Tue, 30 Jun 2020 21:30:57 -0700 (PDT)
Received: from mail-io1-xd2f.google.com (mail-io1-xd2f.google.com [IPv6:2607:f8b0:4864:20::d2f]) (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 1BB8E3A0C66 for <idr@ietf.org>; Tue, 30 Jun 2020 21:30:57 -0700 (PDT)
Received: by mail-io1-xd2f.google.com with SMTP id a12so23564720ion.13 for <idr@ietf.org>; Tue, 30 Jun 2020 21:30:57 -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=4hFPtN6Q+6gymP8Y/JQ9aLv1ZAmkn8SoTktO6WKi2tg=; b=fRPIjyYXyf+RA+gSfB+oiDVJDSy9ANkhWi7a0ny33WJP1Ecp0QT7n8N8jvVIJ7eqp9 ItOnXdWtim0h1jzsdDSriHLP0cQKUh7zAE92J9P9kL9RDR8FpQod2gMZ//2yb6gJRtoJ 0iCNrPXX03XNNgv/bN8GdXnljcRHRTsksl8sDw+Dt8tlZhrnOCDEnpqEowrp7q8XyaaC BYItamJEfa/ZqPer72TfAfMXF+KQSHCpY2ja05STwP3ByQLTaLsb/8AENSwgeFREg1Hx RcRNS52oG+yCxBiiyrBh0KhUqIJTAWEkY5V5yY+0fpyyL3by2+MQWi1P1Rw2mFGixC6p dw7A==
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=4hFPtN6Q+6gymP8Y/JQ9aLv1ZAmkn8SoTktO6WKi2tg=; b=A5eSfaM9SmNchEExQSjLjXeHis2jcWLOkdsbVYYonTlW+DjTB9apYKMymynZcpBXJN S+6aoyqYYOy7p+sXOMosidlTmsKLXS4SJLHXld/D6404mB/lF7MJE9s8J/D2+I+lxlM/ 8CnSO7/fz6DBa4+cotOI/1nBkHyQ+zsY761u5UYtIi1KPhv/525/bZ8MrpOYaDer9G3Q YEA6cuFV6DVzZbxIW2y0SPMoWk0v4km0uAmsSLmQKQ06LmqQussVTpi3J8ReHjJ22DKg vEQrLSvqaRWHR/z9wVthDE0yGK8iYlhEVx39t0bJsCVAh3q1PU04pbrqvwNfS7UGlQU+ eXbQ==
X-Gm-Message-State: AOAM530CSbbrN4tG4YstY9UwFDHYDzAFh0klGjRWBWDawb2z0Qq/8vZz uxmC8nuqj1GJveXsVJJV6ElrQgOELIRsj1l91/Y=
X-Google-Smtp-Source: ABdhPJwQDOFOH8Q16yqkYsxzR6QI14CYcnFEYun9OY7wK9p4iytSbuHvVONu8KxN2BsvHzM9X/BqCb6TF0izgMReN+o=
X-Received: by 2002:a02:cb59:: with SMTP id k25mr26689494jap.112.1593577856306; Tue, 30 Jun 2020 21:30:56 -0700 (PDT)
MIME-Version: 1.0
References: <159174295808.20598.10881535719552756514@ietfa.amsl.com> <CABNhwV0BzBWXmcn+ge9AXBZ69bg_3ht74YoFW8rRLi5A5pjdsw@mail.gmail.com> <CABNhwV2FDXpR3dOZwnJTp_P_iC+Hi8W2NtRXjLcNJJo6M4bXxg@mail.gmail.com> <MN2PR13MB3117DD76779455FEEC34968CF2940@MN2PR13MB3117.namprd13.prod.outlook.com> <MN2PR13MB31177858AB89433F8086D46AF26E0@MN2PR13MB3117.namprd13.prod.outlook.com> <4d4f462181b247f8ae657767a5a8f25a@huawei.com> <MN2PR13MB31178D45D9B276C509891DB5F26F0@MN2PR13MB3117.namprd13.prod.outlook.com> <BY5PR13MB3110FE2D86251F504C0067C2F26C0@BY5PR13MB3110.namprd13.prod.outlook.com>
In-Reply-To: <BY5PR13MB3110FE2D86251F504C0067C2F26C0@BY5PR13MB3110.namprd13.prod.outlook.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Wed, 01 Jul 2020 00:30:45 -0400
Message-ID: <CABNhwV29Q59wr8G2-QrJZqmtLEnW=_Rra2M73AE4sF40+-rk0w@mail.gmail.com>
To: Huaimo Chen <huaimo.chen@futurewei.com>
Cc: "idr@ietf.org" <idr@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000c13d105a959c256"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/scCEzmZqOQm29ESUgyLULB4G6ro>
Subject: Re: [Idr] I-D Action: draft-ietf-idr-rpd-05.txt
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: Wed, 01 Jul 2020 04:31:00 -0000

Hi Huaimo

Few more questions in-line

Thank you

Gyan

On Tue, Jun 30, 2020 at 8:53 PM Huaimo Chen <huaimo.chen@futurewei.com>
wrote:

> Hi Gyan,
>
>     Thank you very much for your comments.
>
>     Our answers/explanations are inline below with prefix [HC].
>
> Best Regards,
> Huaimo on behalf of authors
> ------------------------------
>
> *From:* Idr <idr-bounces@ietf.org> on behalf of Gyan Mishra <
> hayabusagsm@gmail.com>
> *Sent:* Monday, June 22, 2020 7:15 PM
> *To:* idr@ietf.org <idr@ietf.org>
> *Cc:* i-d-announce@ietf.org <i-d-announce@ietf.org>
> *Subject:* Re: [Idr] I-D Action: draft-ietf-idr-rpd-05.txt
>
>
>
>
>
> Authors
>
>
>
> Few comments
>
>
>
> In the abstract and introduction it mentions adjusting traffic.  When
> reading the abstract and introduction adjusting traffic the first thing I
> think of when saying adjusting is BGP QOS QPPB policy to rate limit BGP
> traffic.
>
>
>
> [HC]: It seems that the way (or say RPD) in which the traffic is adjusted
> in the draft and BGP QOS QPPB are different. The BGP QOS QPPB is based on
> configurations or commands. Different configurations for different parts of
> the network need to be done. These configurations combined with the BGP
> propagation provides some QoS policy on some traffic. The RPD provides a
> way to adjust the traffic (i.e., adjust the route attributes to redirect
> the traffic to the less used links) automatically without those
> configurations on different parts of the network.
>

    Gyan> The point here I was trying to make is that in the intro and
draft you mention adjusting traffic to me that means BGP QOS rate limiting
which may also be accomplished by RPD, but I think what may better
represent RPD is stating RPD accomplishes the goal of automated update of
 complex multi active routing policy using a centralized PCE controller
using large communities atoms containers for policy granularity and
flexibility.

https://tools.ietf.org/html/draft-ietf-pce-pcep-extension-native-ip-05


>
>
> In general routing policy is pretty straight forward with active / backup
> routing policy.
>
>
>
> However when optimal active/ active all active routing optimization is
> required where geographic region based routing is desired and if routing
> control optimization is desired between both peering AS’s , the policy can
> become very complex and unmanageable.  If routing control policy is on one
> side only, the other side AS back hauls based on peering policy the policy
> is complex but manageable.  However optimized routing so both sides of
> peering does not back haul can be very complex.
>
>
>
> There are many peering scenario and this one above  is a dual transit as
> all active peering policy scenario.
>
>
>
> The above relates to AFI /SAFI 1/1 2/1 and can be accomplished with
> standard communities.
>
>
>
> [HC]: The above can be achieved using standard communities, but can be
> very complex as you said. Using the RPD in stead of the standard
> communities can reduce the complexity greatly and can adjust the route
> attributes without configurations for some parts of the network to redirect
> the service traffic from the heavy-loaded links to the links with light
> traffic. Thus the network resource is effectively used and the QoE is
> improved. For example, in one metro area network without using the RPD,
> planning and implementing a redirection of a service traffic (coming to and
> exiting from a router) takes days. After the RPD is deployed in the network
> with a controller NCE, this takes just minutes instead of days.
>
>
>
>
> I would say auto adjustment of active routing paths routing where routing
> control is required on both sides of peering to enable optimized paths
>
>
>
> [HC]: The RPD can be used for automatically adjusting active routing paths
> on the both sides of a peer if it is required and permitted. In the case
> where the two sides of a peer are two different ISPs (say ISPa and ISPb)
> and each side (ISP) does not allow the other to control its network, when
> ISPa adjusts routing paths, it can not control the network owned by ISPb
> directly.
>

   Gyan> Understood.  In this particular case it would have to be
coordinated as exchange is between administrative domains, but in this case
RPD automatic large communities policy update can be accomplished via
centralized PCE controller.

I noticed you have AFI/SAFI codepoint request for RPD.  Would this be just
a SAFI request similar to any other SAFI such as BGP flowspec safi 133 134

https://www.iana.org/assignments/safi-namespace/safi-namespace.xhtml

It would nice to see maybe in an appendix an example of the large
> communities atoms containers of the RPD automated proxy use case of how a
> complex policy translated into RPD policy provides tremendous simplicity in
> provisioning policy updates.
>
>
>
> Kind Regards
>
>
>
> Gyan
>
>
>
>
> <https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.verizon.com%2F&data=02%7C01%7Chuaimo.chen%40futurewei.com%7C07a9442b208a4e85cc3108d81c9b0415%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637290799405571469&sdata=wTNqdsqeXJVkHqK%2FZ0iIDAstepTYRxWtDoxX%2FSOg9HY%3D&reserved=0>
>
>
> <https://www.google.com/maps/search/13101+Columbia+Pike+%0D%0A+Silver+Spring,+MD?entry=gmail&source=g>*Gyan
> Mishra*
>
> *Network Solutions Architect *
>
>
>
> *M 301 502-1347 13101 Columbia Pike
> <https://www.google.com/maps/search/13101+Columbia+Pike+%0D%0A+Silver+Spring,+MD?entry=gmail&source=g>
> *Silver Spring, MD
> <https://www.google.com/maps/search/13101+Columbia+Pike+%0D%0A+Silver+Spring,+MD?entry=gmail&source=g>
>
>
>
-- 

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

*Gyan Mishra*

*Network Solutions A**rchitect *



*M 301 502-134713101 Columbia Pike *Silver Spring, MD