Hello,

I have been selected as the Routing Directorate reviewer for this draft. The Routing Directorate seeks to review all routing or routing-related drafts as they pass through IETF last call and IESG review, and sometimes on special request. The purpose of the review is to provide assistance to the Routing ADs. For more information about the Routing Directorate, please see https://wiki.ietf.org/en/group/rtg/RtgDir

Although these comments are primarily for the use of the Routing ADs, it would be helpful if you could consider them along with any other IETF Last Call comments that you receive, and strive to resolve them through discussion or by updating the draft.

Document: draft-ietf-idr-node-target-ext-comm-03
Reviewer: Julien Meuric
Review Date: 2026-09-07
Intended Status: Standards Track

_Summary_

I have some minor concerns about this document that I think should be resolved before publication.


_Comments_

This documents specify a simple extensions to BGP and includes the rational to motivate it. Though the technical definition is fine, the companion text deserves some improvement to bring it to an unambiguous level.


_Minor Issues_

- In section 3, the selected wording looks like an attempt to circumvent RFC 2119 keywords: is it really the intent?
- Section 2 says "The sub-type of the Node Target Extended Community is TBA". Then the IANA section says "IANA assigns the sub-type value 0x09" (twice). Looking at the registries, I see there was an early allocation. It seems to me that:
    * the Figure 1 should reflect this value,
    * the IANA section should rather say something like "Per the early allocation process, the IANA has already assigned the sub-type value 0x09 for..."


_Nits_

Abstract:
- s/generic mechanism of designating the target nodes/generic mechanism to designate the target nodes/

1. Introduction:
- s/save the resources/save resource/
- s/generic mechanism of designating the set of nodes/generic mechanism to designate the set of nodes/
- s/the matching or any of/the matching of any of/
- s/the control of VPN route to VRF import/the control of VPN route in VRFs/
- s/the target of the BGP routes./the target of the BGP information./  [The included example of BGP Flow Spec rules doesn't really fall into the "route" category.]

3. Procedures:
OLD
If the target BGP Identifier in any of the Node Target extended community matches with the local BGP Identifier, this node is one of the target nodes of the Update, the information in the Update is eligible to be kept and installed on this node. If the target BGP Identifier in any of the Node Target extended community does not match with the local BGP Identifier, this node is not the target node of Update, and the information in the Update is not eligible to be installed on this node.
NEW
If the target BGP Identifier in any of the Node Target extended community matches with the local BGP Identifier, this node is one of the target nodes of the Update: the information in the Update is eligible to be installed on this node. If none of the Target BGP Identifiers included in the Node Target extended community matches with the local BGP Identifier, this node is not among the targets of the Update, and the information in the Update is not eligible to be installed on this node.


Regards,

Julien