[RTG-DIR] Rtgdir early review of draft-ietf-bess-bgp-multicast-05

Ben Niven-Jenkins via Datatracker <noreply@ietf.org> Fri, 10 November 2023 21:21 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: rtg-dir@ietf.org
Delivered-To: rtg-dir@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 83CE3C1B0324; Fri, 10 Nov 2023 13:21:56 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Ben Niven-Jenkins via Datatracker <noreply@ietf.org>
To: rtg-dir@ietf.org
Cc: bess@ietf.org, draft-ietf-bess-bgp-multicast.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 11.14.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <169965131652.10617.16191361979113003217@ietfa.amsl.com>
Reply-To: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
Date: Fri, 10 Nov 2023 13:21:56 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-dir/5BebD-QR83otyNnEVjQ3iPFV60Y>
Subject: [RTG-DIR] Rtgdir early review of draft-ietf-bess-bgp-multicast-05
X-BeenThere: rtg-dir@ietf.org
X-Mailman-Version: 2.1.39
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-dir/>
List-Post: <mailto:rtg-dir@ietf.org>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Nov 2023 21:21:56 -0000

Reviewer: Ben Niven-Jenkins
Review result: Has Nits

Hello

I have been selected to do a routing directorate “early” review of this draft.
https://datatracker.ietf.org/doc/draft-ietf-bess-bgp-multicast/

The routing directorate will, on request from the working group chair, perform
an “early” review of a draft before it is submitted for publication to the
IESG. The early review can be performed at any time during the draft’s lifetime
as a working group document. The purpose of the early review depends on the
stage that the document has reached.

For more information about the Routing Directorate, please see
https://wiki.ietf.org/en/group/rtg/RtgDir

Document: draft-ietf-bess-bgp-multicast-05.txt
Reviewer: Ben Niven-Jenkins
Review Date: 10 November 2023
Intended Status: Standards Track

Summary: This document is basically ready for publication, but has nits that
should be considered prior to being submitted to the IESG.

Comments: The document is well written and easy to read and understand.

Nits:

Section 1.2.4 - “For unlabeled (x,g) unidirectional trees, the upstream peer
MAY prefer LAN interfaces to send traffic, since multiple downstream peers may
be reached simultaneously, or it may make a decision based on local policy,
e.g., for load balancing purpose.”

I do not understand why the first MAY is capitalised. Is this a mistake and it
should be in lowercase like the other instances of may in that sentence?

Section 1.2.5 - “PIM and BGP MUST not be used simultaneously between two
neighbors for multicast purpose, and routers connected to the same LAN MUST be
transitioned during the same maintenance window.”

I think the “MUST not” should be “MUST NOT”?

Thanks
Ben