IETF Logo Mail Archive

Re: [GROW] Genart telechat review of draft-ietf-grow-bgp-reject-07

"Hankins, Greg (Nokia - US)" <greg.hankins@nokia.com> Mon, 22 May 2017 22:28 UTC

Return-Path: <greg.hankins@nokia.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99238128C81; Mon, 22 May 2017 15:28:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.746
X-Spam-Level:
X-Spam-Status: No, score=0.746 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 HEkaekXHob2F; Mon, 22 May 2017 15:28:14 -0700 (PDT)
Received: from elasmtp-galgo.atl.sa.earthlink.net (elasmtp-galgo.atl.sa.earthlink.net [209.86.89.61]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C050E1272E1; Mon, 22 May 2017 15:28:13 -0700 (PDT)
Received: from [24.125.34.202] (helo=misfits.twoguys.org) by elasmtp-galgo.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <greg.hankins@nokia.com>) id 1dCvoC-0008Jk-3N; Mon, 22 May 2017 18:28:12 -0400
Received: from misfits.twoguys.org (localhost.twoguys.org [127.0.0.1]) by misfits.twoguys.org (8.14.7/8.12.11) with ESMTP id v4MMSBUQ019945; Mon, 22 May 2017 18:28:11 -0400
Received: (from ghankins@localhost) by misfits.twoguys.org (8.14.7/8.14.7/Submit) id v4MMSBtI019944; Mon, 22 May 2017 18:28:11 -0400
X-Authentication-Warning: misfits.twoguys.org: ghankins set sender to greg.hankins@nokia.com using -f
Date: Mon, 22 May 2017 18:28:11 -0400
From: "Hankins, Greg (Nokia - US)" <greg.hankins@nokia.com>
To: "Dale R. Worley" <worley@ariadne.com>
Cc: draft-ietf-grow-bgp-reject.all@ietf.org, gen-art@ietf.org, grow@ietf.org, ietf@ietf.org
Message-ID: <20170522222811.GA19849@nokia.com>
References: <20170522110448.3obnrbam2who3n5x@hanna.meerval.net> <87y3topre5.fsf@hobgoblin.ariadne.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <87y3topre5.fsf@hobgoblin.ariadne.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-ELNK-Trace: 176464c9115cf5b39c7f779228e2f6aeda0071232e20db4db553864b6c9c9b6404df6b5bffd3c947350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 24.125.34.202
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/_aWJonwEnEkh931g-rIuztvu2Z8>
Subject: Re: [GROW] Genart telechat review of draft-ietf-grow-bgp-reject-07
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 May 2017 22:28:16 -0000

On Mon, May 22, 2017 at 04:29:06PM -0400, Dale R. Worley wrote:
>I suspect my problems come from not realizing there has been a change of
>focus.  (It may be much clearer to routing people.)  So I would suggest
>expanding the title of Appendix A to "Transition Considerations for
>Vendors of BGP Implementations".

Hi Dale, how about simply "Transition Considerations for BGP Implementers" as
there are many excellent FOSS implementations in addition to implementations
sold by vendors?

>    For an implementer, transitioning to a compliant BGP implementation
>    may require a software development and release process that can take
>    several years.
>
>Perhaps "a software development and release" can be omitted.

Updated: For an implementer, transitioning to a compliant BGP implementation
may require a process that can take several years.

>> This document updates [RFC4271] so that routes are neither imported nor
>> exported unless specifically enabled by configuration.  The solution
>> reduces the consequences of these problems, and improves the default level
>> of Internet routing security.
>
>In that case, I'd start the second sentence with "This change ..." or
>perhaps "This update ..." -- nothing has previously been labeled a
>"solution", so the reader has to search a bit to determine the
>antecedent.

Updated: This change reduces the consequences of these problems, and improves
the default level of Internet routing security.

We'll wait to send a new diff in case there are further comments.

Kind regards,
Greg

--
Greg Hankins <greg.hankins@nokia.com>
Senior Product Manager
IP/Optical Networks, Nokia

v2.23.0 | Report a Bug | By Email