[Pce] draft-ietf-pce-pcep-extension-native-ip-14.txt

Susan Hares <shares@ndzh.com> Mon, 26 July 2021 23:19 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 903503A09E5; Mon, 26 Jul 2021 16:19:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.95
X-Spam-Status: No, score=0.95 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id NuqJ4lexLiR8; Mon, 26 Jul 2021 16:19:15 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ACC093A09E3; Mon, 26 Jul 2021 16:19:14 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=;
From: "Susan Hares" <shares@ndzh.com>
To: <pce@ietf.org>
Cc: "'idr-chairs'" <idr-chairs@ietf.org>, "'pce-chairs'" <pce-chairs@ietf.org>
Date: Mon, 26 Jul 2021 19:18:54 -0400
Message-ID: <004a01d78274$a0057b50$e01071f0$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_004B_01D78253.18F58900"
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
Thread-Index: AdeCZyR0c5ST9qe0TaeLxBllu+f5Rg==
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/Lvj2KNS6-qBA8ewiDQVF38QlR58>
Subject: [Pce] draft-ietf-pce-pcep-extension-native-ip-14.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: Mon, 26 Jul 2021 23:19:20 -0000



Thank you for your work on draft-ietf-pce-pcep-extension-native-ip-14.txt.

This comment should be consider feedback from me as a WG member of IDR and
PCE.  I have posted this information also on the  


This draft takes a step toward auto-configuration of BGP peers.  IDR has
created a set of requirements for BGP auto-configuration for Data Centers



I’ve put a copy of these comments at: 




Cheers, Sue 


Comments on draft-ietf-pce-pcep-extension-native-ip-14


Overview of errors 

1) section 6 description of BGP routers needs clarification 

(sections 6.1, 6.2, and 6.3) for RR and RR Clients 

2) BGP Session Establish Procedures – are these restrict to RR and RR

3) Explicit routes [section 6.2] – Is ECMP support as well as 1 prefix/1
next Hop?  

4) IPv4/IPv6 restrictions [section 6.3] – are you restricting the peer
session or the AFI/SAFI supported by the Peer session? 

5) Sections 7, 9, and 10 – may need to change based on your answers to
questions 1-4? 


Detailed questions 


1. Section 6 – sub sections 6.1, 6.2 and 6.3. 



The text that describe the BGP peers and the diagram needs clarification on
the BGP peering between BGP peers:  R1, R7, and R3. If R1 and R7 are Route
Reflector clients (RR clients) are attached to the R3 then it is important
to indicate this point.  If you are using classic route reflection, then R1,
R3 and R7 would need to be in the same Autonomous system. 

The RR (R3) determines what routes are sent to the RR clients.  


This problem impacts the text in section 6.1, 6.2, and 6.3 


2.) Text change for Section 6.1 – if R1 and R7 are RR clients. 


Here’s a change if R1 and R7 are Router Reflector Clients.  


Current text: /

   The PCInitiate message should be sent to PCC which acts as BGP router

  and route reflector(RR).  In the example in Figure 1, it should be

   sent to R1(M1), R3(M2 & M3) and R7(M4), when R3 acts as RR./


Improved text: /

   The PCInitiate message should be sent to PCC which acts as 

    BGP router reflector or a route reflector client. In the 

   example in Figure 1, it should be

   sent to the route reflector clients R1(M1) and R7 (M4), and 

  the route reflector R3 (M1 or M4). PCInitiate creates an 

  auto-configuration function for these BGP peers providing 

  the indicated Peer AS and the Local/Peer IP Address.   /


3) Section 6.1 – BGP Session Establishment Procedure 

Question: Does the PCEInitiate (message and report) require the RR and RR
client structure? 


If so, the PCInitiate should have a parameter indicate what type of BGP peer
(RR or RR client) each receiving BGP peer should be.   


4) Section 6.2 – Explicit Route Establishment Procedure 


Problem: It is unclear what the impact to the routing system of the setting
of explicit route.  


Basic Details: (1 Route with 1 Next Hop)

If R1 and R7 are RR clients and the Explicit route operates as static route
installed by the PCIntiate, then BGP peer will reflected these static routes

[R1 (explicit route [static route]) à R3] 

[R1 (explicit route [static route]) à R3] 


Setting or clearing the Explicit route seem to map to a setting/clear a
static route on the node.  If this is true, then this section needs to be
rework to clear describe the process. 


Your setting the route on the pathway hop by hop is similar to
netconf/restconf setting routes in a pathway.   


ECMP Details: (1 Route with multiple Next Hop) 

If the explicit route is a ECMP route with multiple next hop paths, the next
hop for a route installed in could be R5 or R2. 


If ECMP is allowed, then you need to decide if:

a) adding this route allows the route to be installed if only some of the
next hops are valid (for example R5 is valid, but R2 is not)

b) delete routing allows the route to be deleted if both next hops were not


5) Section 6.3 


Problem:  You do not clear indicate the status of BGP peer routers. 


If R1 and R7 are BGP route reflector clients, then R1 and R7 will send the
route to R3 which will reflect the route to other RR clients (if policy


6.) Section 6.3 

Problem:  It is unclear why there is a restriction for IPv4 prefix to be
sent only via a IPv4 BGP section, and the IPv6 prefix only via a IPV6


Details: I think the author is trying to describe the peers support for a
particular set of AFI/SAFIS for NLRI sent rather than the peering.  However,
it is unclear. 


7.) Sections 7.2 and 7.3 

All of these issues on the intent of the protocol need to be answered before
I can provide additional feedback on the PCEP objects.  


The initial shape of the PCE discussion are reasonable, but working through
the details requires clarity in sections 6.1 to 6.3.  For example, support
for ECMP in the explicit routes may cause sections 7.3 and 7.4 to be


8.) Section 9 – 

The error handling must consider the RR to RR client distribution of routes.

Also, if one PCE overwrites another multiple route are sent from a RR client
to the RR.  The policy in the RR must be set-up to handle errors. 


This section needs a bit of rethinking. 


8.) Section 10 - BGP Considerations -  

The content of the BGP consideration sections seems reasonable, but it
should be reviewed again after all the remainder of the document has been