[Idr] draft-ietf-idr-nhc-00 early Opsdir review

Giuseppe Fioccola via Datatracker <noreply@ietf.org> Mon, 16 February 2026 09:32 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: idr@ietf.org
Delivered-To: idr@mail2.ietf.org
Received: from [10.244.6.246] (unknown [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id B5F35B83D553; Mon, 16 Feb 2026 01:32:49 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Giuseppe Fioccola via Datatracker <noreply@ietf.org>
To: ops-dir@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.59.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <177123436962.678645.6106281461947217541@dt-datatracker-6ff7c68975-7k42g>
Date: Mon, 16 Feb 2026 01:32:49 -0800
Message-ID-Hash: BEN7YGUWVOQA3ISMYZBZRULEFJNV2BMR
X-Message-ID-Hash: BEN7YGUWVOQA3ISMYZBZRULEFJNV2BMR
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-idr.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-idr-nhc.all@ietf.org, idr@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: Giuseppe Fioccola <giuseppe.fioccola@huawei.com>
Subject: [Idr] draft-ietf-idr-nhc-00 early Opsdir review
List-Id: Inter-Domain Routing <idr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/-t4E61Dj23EymsXdsnHp7fxdzsY>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Owner: <mailto:idr-owner@ietf.org>
List-Post: <mailto:idr@ietf.org>
List-Subscribe: <mailto:idr-join@ietf.org>
List-Unsubscribe: <mailto:idr-leave@ietf.org>

Document: draft-ietf-idr-nhc
Title: BGP Next Hop Dependent Characteristics Attribute
Reviewer: Giuseppe Fioccola
Review result: Has Nits

Hi,

I have been selected as the Operational Directorate (opsdir) reviewer for this
Internet-Draft.

The Operational Directorate reviews all operational and management-related
Internet-Drafts to ensure alignment with operational best practices and that
adequate operational considerations are covered.

A complete set of _"Guidelines for Considering Operations and Management in
IETF Specifications"_ can be found at
https://datatracker.ietf.org/doc/draft-opsarea-rfc5706bis/.

While these comments are primarily for the Operations and Management Area
Directors (Ops ADs), the authors should consider them alongside other feedback
received.

- Document: draft-ietf-idr-nhc-00

- Reviewer: Giuseppe Fioccola

- Review Date: 2026-02-16

- Intended Status: Standards Track

---

## Summary

- Has Nits: This document is on the right track but has nits that should be
considered.

## General Operational Comments Alignment with RFC 5706bis

> This document defines a BGP transitive attribute called Next Hop Dependent
Characteristics Attribute (NHC). When a route is propagated beyond the
immediate peer, NHC allows to advertise further certain characteristics about
forwarding plane features.

> The Operational Considerations section is missing and could be included.
However, it is noted that there are already considerations regarding NHC
deployment and operation (sections 2.2, 2.3, 2.4, 2.5) and regarding BGPID TLV
operation (sections 3.2, 3.3, 3.4).

> Section 2.5 is titled "Network Operation Considerations" but I think that the
title does not fully match the content. I would change it or extend the section
to cover more deployment and operational aspects, as suggested in the next
bullet.

> An Operational Considerations section may be included before the IANA
Considerations section. The new section could put together or just refer to the
relevant sections in order to cover deployment and operational aspects, for
example sections 2.2, 2.3 and 2.4 provide deployment information, like the NHC
propagation and regeneration that allow to introduce it into a network
incrementally.

## Major Issues

> No major issues found.

---

## Minor Issues

> From an OPSDIR point of view, there are several deployment considerations in
the text. However, I would suggest to revise Section 2.5 or add a dedicated
Operational Considerations section.

---

## Nits

> I suggest to change the title of Section 2.5 from "Network Operation
Considerations" to "Anycast Next Hops".

> For the IANA Considerations section, I think that this document should only
request the values defined in it. Therefore, Table 2 should not include values
defined in other drafts.

> In the Security Considerations, it could also be mentioned the application to
limited domains (RFC 8799).

---