Re: [Idr] IETF LC for IDR-ish document <draft-ietf-grow-bgp-reject-05.txt> (Default EBGP Route Propagation Behavior Without Policies) to Proposed Standard

[Jeffrey Haas <[e-mail]>]

On Wed, Apr 26, 2017 at 10:08:44AM -0400, Christopher Morrow wrote:
> > And if the end result is what you are doing twice a day why router's can't
> > do it themselves assuming IRRDB or any other src of truth is accurate ?
> >
> >
> 'how often does this data change?'
> 'how often do I want to refresh peering data on devices (from neighbors)'
> 'what is the sla for this part of the service'

I will point out that RPKI-rtr (RFC 6810) is effectively a form of this sort
of dynamic update mechanism. Managing the database and its consistency for
the feed it advertises is certainly no different than what is being talked
about, but the signaling of the *results* is certainly not completely out of
scope of existing or prior work.

It's still gross that RtConfig or equivalent still is the common operational
practice.

-- Jeff