[RTG-DIR] Rtgdir last call review of draft-ietf-bess-evpn-lsp-ping-07
Joel Halpern via Datatracker <noreply@ietf.org> Thu, 16 June 2022 13:47 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 8E2F3C157B47; Thu, 16 Jun 2022 06:47:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joel Halpern via Datatracker <noreply@ietf.org>
To: rtg-dir@ietf.org
Cc: bess@ietf.org, draft-ietf-bess-evpn-lsp-ping.all@ietf.org, last-call@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 8.4.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <165538724257.60857.14871229763796048790@ietfa.amsl.com>
Reply-To: Joel Halpern <jmh@joelhalpern.com>
Date: Thu, 16 Jun 2022 06:47:22 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-dir/opQgatA_qE2DbwxBvMm5ifFA5QY>
Subject: [RTG-DIR] Rtgdir last call review of draft-ietf-bess-evpn-lsp-ping-07
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: Thu, 16 Jun 2022 13:47:22 -0000
Reviewer: Joel Halpern
Review result: Ready
This is a routing directorate review of draft-ietf-bess-evpn-lsp-ping-07
provided by Joel Halpern at the request of the routing directorate review team
leaders as input to the routing area directors. Please treat as any other
review comments.
(Apologies for the delay.)
This document is Ready for publication as a Proposed Standard RFC.
Comments:
Major: None
Minor:
Section 4.1 describes the EVPN MAC Sub-TLV. And states it is derived from
MAC/IP advertisement route. I note that in RFC 7623 (PBB-EVPN) there are
restrictions on several of these fields. Should this section note at least
that in the PBB-EVPN case those restrictions apply (probably with a
pointer, not repeating the restrictions)?
Section 4.4 describes EVPN IP Prefix Sub-TLV. From the wording I suspect
that it applies only to the EVPN case and not to the PBB-EVPN case. In
4.3, the text was explicit about that applicability. Could we be equally
clear here?
- [RTG-DIR] Rtgdir last call review of draft-ietf-b… Joel Halpern via Datatracker
- Re: [RTG-DIR] Rtgdir last call review of draft-ie… Parag Jain (paragj)
- Re: [RTG-DIR] Rtgdir last call review of draft-ie… Parag Jain (paragj)
- Re: [RTG-DIR] Rtgdir last call review of draft-ie… Joel Halpern