[Idr] Warren Kumari's Yes on draft-ietf-idr-rfc5575bis-22: (with COMMENT)
Warren Kumari via Datatracker <noreply@ietf.org> Wed, 22 April 2020 19:09 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: idr@ietf.org
Delivered-To: idr@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 59E873A0B41; Wed, 22 Apr 2020 12:09:09 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Warren Kumari via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-idr-rfc5575bis@ietf.org, idr-chairs@ietf.org, idr@ietf.org, Jie Dong <jie.dong@huawei.com>, aretana.ietf@gmail.com, jie.dong@huawei.com
X-Test-IDTracker: no
X-IETF-IDTracker: 6.127.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Warren Kumari <warren@kumari.net>
Message-ID: <158758254889.29189.17403732838269730397@ietfa.amsl.com>
Date: Wed, 22 Apr 2020 12:09:09 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/JN3zwz7r2l8RwSxwyQvA2C8jf4U>
Subject: [Idr] Warren Kumari's Yes on draft-ietf-idr-rfc5575bis-22: (with COMMENT)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Apr 2020 19:09:10 -0000
Warren Kumari has entered the following ballot position for draft-ietf-idr-rfc5575bis-22: Yes When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-idr-rfc5575bis/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thank you, this is a useful document. I have two minor comments: “ Modern IP routers contain both the capability to forward traffic according to IP prefixes ...” For some reason the “according to IP prefixes” scans oddly to me - the rest of the actions are also (largely) “according to ip prefixes” - this is more of a nit / preference, but I think it would be better to just drop that phrase. “ This specification has removed all references to a opaque-key property. BGP is able to understand the NLRI encoding.” 2 nits: 1: a opaque-key -> an opaque-key (or the opaque-key) 2: BGP is able to... seems a bit odd - BGP is just a protocol, it doesn’t really understand *anything*. I think that a better option would be best “BGP implementations are”. Again this is just a nit, feel free to address it or not...
- [Idr] Warren Kumari's Yes on draft-ietf-idr-rfc55… Warren Kumari via Datatracker