[Idr] RFC 8277 clarifications

Dmytro Shypovalov <dmytro@vegvisir.ie> Wed, 19 November 2025 22:19 UTC

Return-Path: <dmytro@vegvisir.ie>
X-Original-To: idr@mail2.ietf.org
Delivered-To: idr@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 1CB758CCECEF for <idr@mail2.ietf.org>; Wed, 19 Nov 2025 14:19:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.088
X-Spam-Level:
X-Spam-Status: No, score=-2.088 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=vegvisir.ie
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ns9AiZVr8Vmv for <idr@mail2.ietf.org>; Wed, 19 Nov 2025 14:19:29 -0800 (PST)
Received: from mail-ed1-x531.google.com (mail-ed1-x531.google.com [IPv6:2a00:1450:4864:20::531]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id A66D88CCECE8 for <idr@ietf.org>; Wed, 19 Nov 2025 14:19:29 -0800 (PST)
Received: by mail-ed1-x531.google.com with SMTP id 4fb4d7f45d1cf-64180bd67b7so227890a12.0 for <idr@ietf.org>; Wed, 19 Nov 2025 14:19:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vegvisir.ie; s=google; t=1763590768; x=1764195568; darn=ietf.org; h=cc:to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=uJiAAzhhD+8+KyXcMgfxBmKgTGbn8NaYUzVFqJc0vAs=; b=Hg0G+cZYfi+AFuB6kSxiDoYlUMvMNg24bBe1tYuzcbI9hW1SEQQrNhG9aRIxxw8AYA gEXuxuBq/X2ea98hmEEfIWnx6renbmf5Ewcpil7ihrBNF2oovKNiBHvKTJWPFSM3mBcY Cgq4c+Al1w+Vgc8uAdUffFa+bzeZF6uhRSqjhSzwPDCHPSqx/bRr0S9GwVfeFiCHM6ZE 5RfNLphgSz+VnOSuzmISFwWbTtyDnpGJUQGxiNvKTD2uYVts6lrablsvUiSozli7/eGS WWMa5QBYcgbJ6MjlU+weoDfN+fOY4DK7tAeaAorYW+tLJiwjci08M6QuJHRxXqZ3vV3S MECA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1763590768; x=1764195568; h=cc:to:subject:message-id:date:from:mime-version:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=uJiAAzhhD+8+KyXcMgfxBmKgTGbn8NaYUzVFqJc0vAs=; b=CWo4fHgCLUvjTUnBPUoGNS1GUfm++2g4Ked4NpTc4S+eq7wIyF9IbouqHy4DhcmkwP PH24qAhRz/wTLEp6lDEWUGMbHeYG7OqwIPurGg1QKFSbyAfBPacHhRyh1damYAZm83ky 0m8N6RpJTywpYdDi+Aqyky0GZXLPFCgn/adBmP6krVLhiJH5CQZlY/qsB4Hcr9TC1Nao utSEylcWQ86IojuON0SbG2V5Jb1mlsBDkTtpWVqe0yN+Lz80ARFAkTlnyCWqxwa4DOhm Oyl31V3ZS5slXbA/IkhgGE17yM5qE4rBDb0gtPPAYZQDwCZygUbLS+CoiVovJFDcp4i1 jVKg==
X-Gm-Message-State: AOJu0YzB07DpODaOshnoe0eZl9EvkRQ99YDmAhu7ULObgejVVmUwlE2r XtZ364Ide4my+AC+0ro+1bt2SRSKlfTxyNaN00/RkObLb50gid4kMR3OjyAs2mj5w9ujBmvZnfF Dcddc7ANfh0S0jqPiNeonC7dEoT/SaSVgYJlG/zQRqN7I/0EzZ/qsWyY=
X-Gm-Gg: ASbGnct099a4WI8l55gdo0ZhLCH7TvPHyrYCHiy1WvNizr6dtYHwKKTAl9bd+lRPxlo 0HJfNud83vfN2For41AK3ROevIELlcBBDduwjUvW+EQS8JN2DSrgGfADl+GfhY+eLyOAQIw3S5S YN9Yl040oq1D5bWcxYsGqaB5khRwXImpIGX+xgW16f9z/kiwRsZsVPVBMCDhiRB/ETxfX0cxqpM 3PqUsOU9fV1LQBN3umok2RF5jLrUJaUy/eStX3DmcJoPfV4zRBt/CYGAyAxwP1mTELh2rod6M3v c3CmXg==
X-Google-Smtp-Source: AGHT+IG4rjQnWQZKh8iTrsIHRGRSC8DJgzkxKck3K8x2BBBL462MKSZbPs9wHrGjhYF2nNL8uVLbUA2yqiwQXiVolL4=
X-Received: by 2002:a05:6402:4409:b0:643:8301:d136 with SMTP id 4fb4d7f45d1cf-64536459678mr812207a12.19.1763590768002; Wed, 19 Nov 2025 14:19:28 -0800 (PST)
MIME-Version: 1.0
From: Dmytro Shypovalov <dmytro@vegvisir.ie>
Date: Wed, 19 Nov 2025 22:19:16 +0000
X-Gm-Features: AWmQ_blJha16kJuwUKt7daIVbDe4UhuAUlHBiAlYsGoFpyyY9iAocf10dvDAkWk
Message-ID: <CAEBHQ-Ng2anh9oDeZrBqUuY6XWqWWOSF=MhBSYZWZdW=UFnZcw@mail.gmail.com>
To: idr@ietf.org
Content-Type: multipart/alternative; boundary="0000000000004192c80643f9f96d"
X-MailFrom: dmytro@vegvisir.ie
X-Mailman-Rule-Hits: nonmember-moderation
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-idr.ietf.org-0
Message-ID-Hash: GFDJEAHEM2Q6BGZKIM2HPUHILJNYT4CE
X-Message-ID-Hash: GFDJEAHEM2Q6BGZKIM2HPUHILJNYT4CE
X-Mailman-Approved-At: Wed, 19 Nov 2025 14:59:36 -0800
CC: Kyrylo Yatsenko <k.yatsenko@vyos.io>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Idr] RFC 8277 clarifications
List-Id: Inter-Domain Routing <idr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/Gk-kyDTACDQJZYLISO-5aiC5MiE>
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>

Dear IDR WG,

I've been working on an SR-TE project using BGP-LU to influence traffic
engineering paths. This requires the advertisement of multiple labels.

RFC8277 seems to have 2 conflicting statements

Section 2.1:

   the Count is the maximum
   number of labels that the BGP speaker sending the Capability can
   process in a received UPDATE of the specified AFI/SAFI.  If the Count
   is 255, then no limit has been placed on the number of labels that
   can be processed in a received UPDATE of the specified AFI/SAFI.


This assumes the BGP update can have up to 255 labels (in theory).

Section 2.3:

   - Length:

      The Length field consists of a single octet.  It specifies the
      length in bits of the remainder of the NLRI field.

      Note that for each label, the length is increased by 24 bits (20
      bits in the Label field, plus 3 bits in the Rsrv field, plus 1 S
      bit).


If we use BGP-LU with multiple labels for SR-TE, it will always advertise
host routes, which given max 255 bits of NLRI, leaves us with theoretical
maximum of 9 labels for IPv4 and 5 labels for IPv6. The RFC message format
will not be able to support more labels, regardless of platform
capabilities. But I've seen vendor implementations advertising multi label
capability with more labels.

Am I missing something? Is there a way to advertise more labels in BGP-LU?


Regards,
Dmytro