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

[t.petch <[e-mail]>]

----- Original Message -----
From: <[e-mail]>
Cc: "Hares Susan" <[e-mail]>
Sent: Tuesday, April 25, 2017 8:54 AM
> > From: Mikael Abrahamsson [mailto:[e-mail]]
> Sent: Tuesday, April 25, 2017 9:33 AM
> > On Tue, 25 Apr 2017, [e-mail] wrote:
>  >
>  > > If this is indeed the goal to make no protocol change, including
no
>  > > default behavior change in the protocol, could the document be
updated
>  > > to state this. In which case, Standard Track may be required.
>  >
>  > I re-read https://tools.ietf.org/html/draft-ietf-grow-bgp-reject-05
>  >
>  > As far as I can see, it doesn't do any protocol change. It changes
the
>  > default behaviour a router comes with when it comes to treating
routes
>  > sent/received when there is no policy map applied on the neighbor.
>  >
>  > So it suggest a behavioural change, not a protocol change.
>
> So we now have 3 readings:
> - protocol change updating RFC 4271 (base BGP spec)
> - a behavioural change, not a protocol change
> - no default behavior change in the protocol

The current text in RFC 4271 is
"    If the route is learned from an external peer, then the local BGP
      speaker computes the degree of preference based on preconfigured
      policy information.  If the return value indicates the route is
      ineligible, the route .. "

With this I-D, that becomes

"    If the route is learned from an external peer, then the local BGP
      speaker computes the degree of preference based on preconfigured
      policy information.

      If there is no preconfigured policy information, the route is
ineligible.

                                    If the return value indicates the
route is
      ineligible, the route ... "

I think that that is a change that will change what is then transmitted
on the wire so it is a protocol change.  YMMV.

Tom Petch

>  > --
>  > Mikael Abrahamsson    email: [e-mail]
>
>
________________________________________________________________________
_________________________________________________