[Pce] Opsdir last call review of draft-ietf-pce-association-bidir-10
Al Morton via Datatracker <noreply@ietf.org> Wed, 27 January 2021 23:22 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D04A3A0D75; Wed, 27 Jan 2021 15:22:45 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Al Morton via Datatracker <noreply@ietf.org>
To: ops-dir@ietf.org
Cc: draft-ietf-pce-association-bidir.all@ietf.org, last-call@ietf.org, pce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <161178976521.30445.7921080637059611565@ietfa.amsl.com>
Reply-To: Al Morton <acmorton@att.com>
Date: Wed, 27 Jan 2021 15:22:45 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/QzTtDeLc1JhdVdXYCLOtwZvcOXo>
Subject: [Pce] Opsdir last call review of draft-ietf-pce-association-bidir-10
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jan 2021 23:22:45 -0000
Reviewer: Al Morton Review result: Has Nits This document defines PCEP extensions for grouping two unidirectional MPLS-TE LSPs into an Associated Bidirectional LSP. Specifically, this document defines two new Association Types, "Single-sided Bidirectional LSP Association" and "Double-sided Bidirectional LSP Association", as well as "Bidirectional LSP Association Group TLV" to carry additional information for the association. Comments: Thank you for including Section 8, Manageability Considerations. I'm seeking clarification for the following requirement (although it may be completely clear to those who are knee-deep in this terminology): Section 4.1 ... o The Tunnel (as defined in [RFC3209]) of forward and reverse LSPs of the Single-sided Bidirectional LSP Association on the originating endpoint node MUST be the same, albeit with reverse endpoint nodes. as currently written, the requirement says that two preceding nouns MUST be the same. But is it: "The Tunnel *containing the* forward and reverse LSPs..."? Or is it, "The *Tunnels associated with the* forward and reverse LSPs ..." ? Or something else? [RFC3209] simple definitions are (both seem to be unidirectional): LSP Tunnel An LSP which is used to tunnel below normal IP routing and/or filtering mechanisms. Traffic Engineered Tunnel (TE Tunnel) A set of one or more LSP Tunnels which carries a traffic trunk. -=-=-=-=-=-=-=- Another request for clarification: 5.6. State Synchronization During state synchronization, a PCC MUST report all the existing Bidirectional LSP Associations to the Stateful PCE as per [RFC8697]. After the state synchronization, the PCE MUST remove all stale Bidirectional LSP Associations. What is the procedure to determine a stale association, a time-out or simply the absence of a previously association in a report? Is there a passage covering stale determination in 8697, another reference, or a passage in the current memo that I missed? -=-=-=-=-=-=-=- Editorial: 4.2. Bidirectional LSP Association Group TLV The "Bidirectional LSP Association Group TLV" an OPTIONAL TLV for use s/an/is an/
- [Pce] Opsdir last call review of draft-ietf-pce-a… Al Morton via Datatracker
- Re: [Pce] Opsdir last call review of draft-ietf-p… Rakesh Gandhi
- Re: [Pce] Opsdir last call review of draft-ietf-p… MORTON, ALFRED C (AL)
- Re: [Pce] Opsdir last call review of draft-ietf-p… Rakesh Gandhi