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

[Job Snijders <[e-mail]>]

On Sat, Apr 29, 2017 at 01:30:26PM +0900, Randy Bush wrote:
> but ignoring broken analogies and to the point, in the case of this
> draft, the operator is in definite danger of a major oops (that's a
> technical term) when field upgrading the software in a router.
> 
> despite this exposure, i am mostly of the opinion that the benefits
> outweigh the risks with this draft.  but vendors should do their best to
> ameliorate the risks with loud warnings.

In addition to warnings, perhaps some inspiration can be drawn from the
deprecation of SSHv1 in OpenSSH. This too required a process that
spanned several years (and isn't finished yet, since distributions
haven't yet incorporated the latest upstream version of OpenSSH, but
alas). If OpenSSH can do it, so can others! :-)

First: http://undeadly.org/cgi?action=article&sid=20150324200217
Then: http://undeadly.org/cgi?action=article&sid=20170501005206

Considerations of others regarding SSHv1:

    PuTTY: http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/no-ssh1-fallback.html
    Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807107

Kind regards,

Job