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

[Gyan Mishra <[e-mail]>]

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.

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.

I would say auto adjustment of active routing paths routing where routing
control is required on both sides of peering to enable optimized paths

Kind Regards

Gyan

On Fri, Jun 12, 2020 at 2:10 PM Gyan Mishra <[e-mail]> wrote:

>
> Hi Authors
>
> Tracker shows this draft in WGLC state?
>
> Is that correct?
> BGP Extensions for Routing Policy Distribution (RPD)
> draft-ietf-idr-rpd-05
>
>    - Status <https://datatracker.ietf.org/doc/draft-ietf-idr-rpd/>
>    - IESG evaluation record
>    - IESG writeups
>    <https://datatracker.ietf.org/doc/draft-ietf-idr-rpd/writeup/>
>    - Email expansions
>    <https://datatracker.ietf.org/doc/draft-ietf-idr-rpd/email/>
>    - History
>    <https://datatracker.ietf.org/doc/draft-ietf-idr-rpd/history/>
>
>
>    - Versions
>    - 00 <https://datatracker.ietf.org/doc/draft-ietf-idr-rpd/00/>
>    - 01 <https://datatracker.ietf.org/doc/draft-ietf-idr-rpd/01/>
>    - 02 <https://datatracker.ietf.org/doc/draft-ietf-idr-rpd/02/>
>    - 03 <https://datatracker.ietf.org/doc/draft-ietf-idr-rpd/03/>
>    - 04 <https://datatracker.ietf.org/doc/draft-ietf-idr-rpd/04/>
>    - 05 <https://datatracker.ietf.org/doc/draft-ietf-idr-rpd/>
>
> 000102030405000102030405Jul 2015Jun 2016Oct 2018Mar 2019May
> 2020draft-li-idr-flowspec-rpddraft-ietf-idr-rpd
> DocumentType Active Internet-Draft (idr WG
> <https://datatracker.ietf.org/wg/idr/>)
> Last updated 2020-06-10 (latest revision 2020-06-09)
> Replaces draft-li-idr-flowspec-rpd
> <https://datatracker.ietf.org/doc/draft-li-idr-flowspec-rpd/>
> Stream IETF
> Intended RFC status (None)
> Formats  plain text <https://www.ietf.org/id/draft-ietf-idr-rpd-05.txt>
>  pdf <https://tools.ietf.org/pdf/draft-ietf-idr-rpd-05.pdf> htmlized
> (tools) <https://tools.ietf.org/html/draft-ietf-idr-rpd-05> htmlized
> <https://datatracker.ietf.org/doc/html/draft-ietf-idr-rpd-05> bibtex
> <https://datatracker.ietf.org/doc/draft-ietf-idr-rpd/bibtex>
> StreamWG state <https://datatracker.ietf.org/help/state/draft/ietf> In WG
> Last Call
> Document shepherd No shepherd assigned
> IESGIESG state <https://datatracker.ietf.org/help/state/draft/iesg> I-D
> Exists
> Consensus Boilerplate Unknown
>
>
> On Tue, Jun 9, 2020 at 6:50 PM <[e-mail]> wrote:
>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> This draft is a work item of the Inter-Domain Routing WG of the IETF.
>>
>>         Title           : BGP Extensions for Routing Policy Distribution
>> (RPD)
>>         Authors         : Zhenbin Li
>>                           Liang Ou
>>                           Yujia Luo
>>                           Sujian Lu
>>                           Huaimo Chen
>>                           Shunwan Zhuang
>>                           Haibo Wang
>>         Filename        : draft-ietf-idr-rpd-05.txt
>>         Pages           : 18
>>         Date            : 2020-06-09
>>
>> Abstract:
>>    It is hard to adjust traffic and optimize traffic paths on a
>>    traditional IP network from time to time through manual
>>    configurations.  It is desirable to have an automatic mechanism for
>>    setting up routing policies, which adjust traffic and optimize
>>    traffic paths automatically.  This document describes BGP Extensions
>>    for Routing Policy Distribution (BGP RPD) to support this.
>>
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-idr-rpd/
>>
>> There are also htmlized versions available at:
>> https://tools.ietf.org/html/draft-ietf-idr-rpd-05
>> https://datatracker.ietf.org/doc/html/draft-ietf-idr-rpd-05
>>
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-rpd-05
>>
>>
>> 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/
>>
>>
>> _______________________________________________
>> Idr mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/idr
>>
> --
>
> <http://www.verizon.com/>
>
> *Gyan Mishra*
>
> *Network Solutions A**rchitect *
>
>
>
> *M 301 502-134713101 Columbia Pike *Silver Spring, MD
>
> --

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

*Gyan Mishra*

*Network Solutions A**rchitect *



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