[pim] Opsdir last call review of draft-ietf-pim-drlb-13

Joe Clarke via Datatracker <noreply@ietf.org> Wed, 30 October 2019 19:29 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: pim@ietf.org
Delivered-To: pim@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FD331201A3; Wed, 30 Oct 2019 12:29:44 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joe Clarke via Datatracker <noreply@ietf.org>
To: ops-dir@ietf.org
Cc: last-call@ietf.org, pim@ietf.org, draft-ietf-pim-drlb.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.108.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Joe Clarke <jclarke@cisco.com>
Message-ID: <157246378456.32588.13080368226769629725@ietfa.amsl.com>
Date: Wed, 30 Oct 2019 12:29:44 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/8HKwJuKbOQvoPNia5mCt1KATPKs>
Subject: [pim] Opsdir last call review of draft-ietf-pim-drlb-13
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Oct 2019 19:29:45 -0000

Reviewer: Joe Clarke
Review result: Ready

I was asked to review this document on behalf of the ops directorate.  This
document describes a new protocol to do PIM DR load balancing.  In general, I
think this document is ready.  I appreciate both the backwards compat and
operator considerations sections.  In fact, as I read through this, I kept
thinking, "I hope they talk about legacy vs. new routers on the same shared
LAN".  One thing that might be good to add is a callout to vendors/implementors
that they are explicit in which GDR for which group/source.  Thinking with a
troubleshooting mind, this changes the paradigm in forwarding and knowing how
that behaves will be critical.

I also found three really small nits:

Section 5.2.1:

s/ordinal number of router X/ordinal number of Router X/


Section 5.4:



Section 5.8:

s/take part in an load-balancing/take part in load-balancing/