[Gen-art] Genart last call review of draft-ietf-grow-bmp-adj-rib-out-05

Linda Dunbar via Datatracker <noreply@ietf.org> Fri, 14 June 2019 20:44 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DE3AD120286; Fri, 14 Jun 2019 13:44:12 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Linda Dunbar via Datatracker <noreply@ietf.org>
To: <gen-art@ietf.org>
Cc: grow@ietf.org, draft-ietf-grow-bmp-adj-rib-out.all@ietf.org, ietf@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.97.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Linda Dunbar <Linda.dunbar@huawei.com>
Message-ID: <156054505283.28254.9882843194956326237@ietfa.amsl.com>
Date: Fri, 14 Jun 2019 13:44:12 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/_GM5K5YuxAzv_vaJiYqxjqe2QI0>
Subject: [Gen-art] Genart last call review of draft-ietf-grow-bmp-adj-rib-out-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jun 2019 20:44:13 -0000

Reviewer: Linda Dunbar
Review result: Almost Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>;.

Document: draft-ietf-grow-bmp-adj-rib-out-??
Reviewer: Linda Dunbar
Review Date: 2019-06-14
IETF LC End Date: 2019-06-25
IESG Telechat date: Not scheduled for a telechat

Summary:

The draft updates the BGP Monitoring Protocol BMP by adding access to the
Adj-RIB-Out RIBs. There are some unclear areas that need authors to clarify.

Major issues:

Minor issues:

Section 1 last paragraph:
It is not clear if BMP sender send to multiple BMP receivers  or just  to one
"BMP receiver". The first part of the sentence says "..send to a BMP
receivers", the second part says ".. advertise to BGP peers, .."

Suggest to make it consistent, such as sending  to multiple, or just one.   "..
to send to BMP receivers what it advertises.."

Does a BMP sender also send out Adj-RIB-In? it is not clear to.

Section 6 first sentence: just curious which BMP messages are NOT applicable to
Adj-RIB-In or Adj-RIB-out?   If it is specified in other documents, please add
a reference.

Nits/editorial comments:

Thank you.

Linda Dunbar