[Idr] Fwd: I-D Action: draft-dunbar-idr-metadata-subscription-control-00.txt

Robert Raszuk <robert@raszuk.net> Wed, 03 December 2025 22:05 UTC

Return-Path: <robert@raszuk.net>
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 D84A094E6AE5 for <idr@mail2.ietf.org>; Wed, 3 Dec 2025 14:05:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=raszuk.net
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 Hgd7ulLakEjI for <idr@mail2.ietf.org>; Wed, 3 Dec 2025 14:05:46 -0800 (PST)
Received: from mail-ed1-x529.google.com (mail-ed1-x529.google.com [IPv6:2a00:1450:4864:20::529]) (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 34AD994E6AD7 for <idr@ietf.org>; Wed, 3 Dec 2025 14:05:46 -0800 (PST)
Received: by mail-ed1-x529.google.com with SMTP id 4fb4d7f45d1cf-64180bd67b7so318236a12.0 for <idr@ietf.org>; Wed, 03 Dec 2025 14:05:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; t=1764799545; x=1765404345; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=3rSVqzoiRUbKXfAwXyFKN3PhXnDUJLAh3Klk/3f01WU=; b=IGMBPLujg7IY3WKyNvO3+d8OA7sY6DXpfFEhZz+LRkSFvWSNPGwV65YrCgPc6cGui+ 7z/NxAjCfwKY0jEqsOTeHwwuxs4GXNjjZL1knkZAHtz92GO/L6e0QH4CMONP9XoPyt7y bojkE1sniT4HyQISwHfAWaA7SsYf9kihBrlnG2QugsfrKbZzkbBenMBEQatXD//LxtN4 gFqHO5ryurVxDalGA2prbm03W4KhB+Jc3KA9IBG9sIPWeoEhmC/Et4J5wfCCxnbBsm1s /D0DWSn6vBNVHXkTr70ivxFxlb4moRcVIVvVD64Gb+Cyyz4vEoE4A2jLPCz3QbncPlte Ko1g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1764799545; x=1765404345; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=3rSVqzoiRUbKXfAwXyFKN3PhXnDUJLAh3Klk/3f01WU=; b=HcCsCg3S/Q3aAYd0ZHoQcZMmVPwG47F3cK5gP1VaJrauKFpf1M0pUVX8HQX3RqiC1O Rrun/rF9pMxeQip1oA0E4cMMU1iZb1i79vbcYZeewpWhcd8aTUe2Z9SM8G6Vmp/y4pZS 3GmeXAaq7t7LFRLUlLNR+w8kHnFVPHz+WiKweU/3vg1tx1l/KzbVkpu1kTxJEJd1ZaU5 WGMWqYdcKUsYI3heF0cOhvip426fACzESw9gWwHzfM03Fwe+LlT59eenn4Xy01xsRhYx /wiuMednNDUWq8QrLbO3CHzNyx6p3mzOMbkLZ/6BHKoIVCd2z+1m5VTO5KvAesNyAFwX zXFQ==
X-Gm-Message-State: AOJu0YzSYVSFe3Sh+xrhG+/x+hE4v3I+GBU2FjhK44ulTUmd/W5mqQqj St/nutZBuHJLHzKHoRJH8Tfe5uODSnLM5yOAQrQd+ydCSPBfuTMRiYdJxePSMteTpyW6KfIiOJV nMuzihdu7qkFgxDWqsAGCdl3fxyYsbQbw92XWtxTZThVAVswPCvAvrrw=
X-Gm-Gg: ASbGncv+XyFUhHHcWb4OMX1LOQd3FHlxln/tRYrZd+GPw1sx2XS8ae7zgGXPsF8pv7M TLgrap8VFYdejkVljPM5bzXpBy4sJ0HwTUcwBokmqJOCK+tJ/okAB2Qu1jtQ+hML9zs/ZxNwWFa 8ShRg0Q8Gp4L5FOURpMS3hlp1CALNF9INe6j9DXxTFt56n+wlbbYg/lh6QYWE44fxr3eJjSEugz WTgOCecvOXDvZQF12rmFmI/Wi0N
X-Google-Smtp-Source: AGHT+IGBj0lF7EVQ2pyNfQA/9+op30dFYH/E/1MQxDE9ohpufnDJVMnwaAumKlFWg/W3GjOeZciOrbmS3gWpWLi2P6g=
X-Received: by 2002:a05:6402:26c3:b0:643:8301:d136 with SMTP id 4fb4d7f45d1cf-6479c47fe11mr3221893a12.19.1764799545159; Wed, 03 Dec 2025 14:05:45 -0800 (PST)
MIME-Version: 1.0
References: <176479878790.4061714.7341054658780281991@dt-datatracker-5bd94c585b-wk4l4>
In-Reply-To: <176479878790.4061714.7341054658780281991@dt-datatracker-5bd94c585b-wk4l4>
From: Robert Raszuk <robert@raszuk.net>
Date: Wed, 03 Dec 2025 23:05:34 +0100
X-Gm-Features: AWmQ_bmAhVkmBKZa0U1GEVqYx86GQNkjkqikRRibbVoNwuZvrhM-Qp-T9K0zNk4
Message-ID: <CAOj+MMHTp03iZFho4yDBK=i-M=spZaxxk78CW94W3Sm0nxpFoQ@mail.gmail.com>
To: Linda Dunbar <ldunbar@futurewei.com>
Content-Type: multipart/alternative; boundary="000000000000fd412a0645136953"
Message-ID-Hash: MIKP6WTLFHJ6FGZYSCK2STJLQBGWXESO
X-Message-ID-Hash: MIKP6WTLFHJ6FGZYSCK2STJLQBGWXESO
X-MailFrom: robert@raszuk.net
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: "idr@ietf. org" <idr@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Idr] Fwd: I-D Action: draft-dunbar-idr-metadata-subscription-control-00.txt
List-Id: Inter-Domain Routing <idr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/1eq5FoiET45sT1tcRTSa3iR-PBg>
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>

Hi Linda,

Reading this draft I am very confused on the contradicting statements:

3.  Summary of Operation

   An ingress node that wishes to receive service metadata for routes
   tagged with particular Route Targets (RTs) signals its interest by
   advertising one or more MDS NLRI (AFI=IPv4/IPv6, SAFI=TBD-MDS) that
   identify the relevant RTs.

vs

8.  Relationship to RTC (RFC 4684)

   RTC [RFC4684] constrains which routes are propagated to a peer based
   on the RTs that the peer has expressed interest in.  Metadata
   Subscription (MDS) applies a complementary control: it determines
   whether service metadata is included when those routes are
   advertised.  Thus, RTC governs propagation of reachability
   information, while MDS governs propagation of associated service
   metadata.  Both mechanisms may be deployed together.

*Discussion:*

If section 3 is correct then RTC as defined today is all what is needed.

Now I am guessing that what you are trying to do here is to express an
additional signalling in this new SAFI if UPDATE messages containing RTs
signalled by RTC should also carry metadata or not.

But you can easily accomplish that goal by defining a new set of RTs (even
different by one bit) and signal it with RTC.

So why do we need a new SAFI.

*Side comment: *

When I read the first sentence of the Abstract: "   This document specifies
a receiver-driven _Metadata Subscription_ (MDS) mechanism for BGP."  I was
hoping to see actual subscription proposal turning BGP into PUB-SUB for
specific metadata types.

But reading on the text let me down :)

Best,
R.

-------- Forwarded message ---------
From: <internet-drafts@ietf.org>
Date: Wed, Dec 3, 2025 at 10:53 PM
Subject: I-D Action: draft-dunbar-idr-metadata-subscription-control-00.txt
To: <i-d-announce@ietf.org>


Internet-Draft draft-dunbar-idr-metadata-subscription-control-00.txt is now
available.

   Title:   Metadata Constrained Distribution
   Authors: Linda Dunbar
            Alvaro Retana
            Keyur Patel
            Kausik Majumdar
   Name:    draft-dunbar-idr-metadata-subscription-control-00.txt
   Pages:   11
   Dates:   2025-12-03

Abstract:

   This document specifies a receiver-driven _Metadata Subscription_
   (MDS) mechanism for BGP.  A BGP speaker uses the new MDS NLRI to
   subscribe to specific service metadata attributes.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-dunbar-idr-metadata-subscription-control/

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-dunbar-idr-metadata-subscription-control-00

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts


_______________________________________________
I-D-Announce mailing list -- i-d-announce@ietf.org
To unsubscribe send an email to i-d-announce-leave@ietf.org