[Idr] Re: New Liaison Statement, "oLS to IETF on BGP data model"

tom petch <ietfc@btconnect.com> Sat, 22 November 2025 13:20 UTC

Return-Path: <ietfc@btconnect.com>
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 38C778E9A7B8; Sat, 22 Nov 2025 05:20:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, RCVD_IN_MSPIKE_H2=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.com
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 XndZ3SvrtWrt; Sat, 22 Nov 2025 05:20:49 -0800 (PST)
Received: from PA4PR04CU001.outbound.protection.outlook.com (mail-francecentralazon11013037.outbound.protection.outlook.com [40.107.162.37]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 3A44A8E9A7B0; Sat, 22 Nov 2025 05:20:48 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=XBO2XFweLasp1aG5eo6pd6l1qplqQHv1Mx0MeFuwAUk+cnuJuNfdqes7+ZMit7YwehgAnkP93B9VSxwJHuEFhREZEVSgZjNvOChSr+N2cMkZKdAZqpWOI3CuFc/RjN7XMk5qDrsEec/7bvOmqmvn8ljBYsSAUytRNYOkoiN/0N3+NuvUL6xcxAn0mIREbx9ZUdiflKHETlyjg7Rst/cw8n91NqKdzHjPbCXGd69YxqGdPgg9Oa/uXafFRBVDzpWtnLdo9rcL9G9trG1Q75Jw6XrAC3qrbmEmbJ7fNt5ljTxuLCjttoAPGy3R5pIQMCgPsWCFEe0HvG6C8W34NKfPVA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=l9QPqvR0sudDKPyz7xvZuXpEYZ0VI+qQrhqgHVuNHnM=; b=swkKOqguY4+vrC0jAPdqgA+j/pWzs0KkJt5sdWgCXOfM6T9LQx3i6VX2D095srKjDB5qwKF73TJDEjb6D0jycVxCpatwV5NG+Ky1kdLIWuMPziFwHSV/AfNnPSqGjWaWH2pgVBdWhRpsn5QD4Kn/jcPlHKrbFS3x1fMP9rni6eXvt8ZY4+TBTlS2AbsEaXig+AC8Y5qyd3ql3Xtqr4yxPwR7U0P3vc2u2K4xYheL+FsZjJoR7/iIsBbqC8gj7QsotA2+LUkT/852ni2WsnBxfceL80aeR+IBf/U/Bv/KnOFK6xicpjDu+ZlyL/6GByKxKGANusZ8KhdFBveosdYrVg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=l9QPqvR0sudDKPyz7xvZuXpEYZ0VI+qQrhqgHVuNHnM=; b=BiyKmcrGIsuOD3XSM3F6QBCqcsOl84Nuko2WPzfpH3/Y5PQXN9UXMPu7aSEwJS5hWpof89uvJ3bY/4+5+XLF/vQd+3JSdOQWgLHDnkZQpbmxRho+8Y/yqjuicCoQr6GQ9umT8w0lEMuX1fw+fO7xeKJROXqWysUoUcntc1tgxks=
Received: from DB9PR07MB7946.eurprd07.prod.outlook.com (2603:10a6:10:2ad::20) by AM8PR07MB7620.eurprd07.prod.outlook.com (2603:10a6:20b:245::23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.9343.14; Sat, 22 Nov 2025 13:20:40 +0000
Received: from DB9PR07MB7946.eurprd07.prod.outlook.com ([fe80::36c7:2d1c:5949:505a]) by DB9PR07MB7946.eurprd07.prod.outlook.com ([fe80::36c7:2d1c:5949:505a%7]) with mapi id 15.20.9343.011; Sat, 22 Nov 2025 13:20:39 +0000
From: tom petch <ietfc@btconnect.com>
To: Ketan Talaulikar <ketant.ietf@gmail.com>, Inter-Domain Routing Discussion List <idr@ietf.org>
Thread-Topic: [Idr] Re: New Liaison Statement, "oLS to IETF on BGP data model"
Thread-Index: AQHcW4FLzeq6Xcp1rkK7WM7mT2kzMbT+qhEs
Date: Sat, 22 Nov 2025 13:20:39 +0000
Message-ID: <DB9PR07MB7946151FC06D2C52E176D7E6A0D2A@DB9PR07MB7946.eurprd07.prod.outlook.com>
References: <176377917609.1807088.18231834189018308158@dt-datatracker-5bd94c585b-wk4l4> <CAH6gdPwpL59w6tPxvTqbExUExRYotSETQFt3sFJwGdNEr47y2w@mail.gmail.com>
In-Reply-To: <CAH6gdPwpL59w6tPxvTqbExUExRYotSETQFt3sFJwGdNEr47y2w@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels:
authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=btconnect.com;
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: DB9PR07MB7946:EE_|AM8PR07MB7620:EE_
x-ms-office365-filtering-correlation-id: 1a66fd08-b740-46d4-bf59-08de29c9ee7c
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;ARA:13230040|1800799024|376014|366016|38070700021;
x-microsoft-antispam-message-info: 8DQm6L2Yqi9pEEqBMtKDaN+Qox4VjYy1UynguWT+eH66aEhVtJeB1uGq7OIYL6TWxJpcqCDDcFtokweOwgDRVG4/MUZo7wQepvn3tFOYdQRs4Ozl2EjB0w0gfXAjSOzqEKnPM8L+8htl31gzpf6HtSuqipRzdMRedm8shBeBCgyCll/MYILgDz13QI0tyJUeEhFMZh9T0qdin2WkOB6ycnVi7ycIZ50SfGaO0q0lxaHslPuP7RlLF2NSARMJRrVBigEf2SBpLh2AQd/ljyYWGiTB2naiJWEGGMvF26ZQROgfC4b9Yv5jbKdk7TZUrW3m97S2j0nbWbLrhk2szPFSCsusGKEJ9ye0G3vGI1L5LghLbK24BxYe7M/WZyYG/ZMquGVdfKwpC3a4sktvOiFD0s6iajcgahT/iGJ5d9B8U3kR1zjRAURsAPPAgnLyttzVl4qhfWwsbvKMwXuM3OWsQlUU6JLANH143sIV9KQIsJhck07vnSdjDQ7ZD4yJcYtDkwn9w9LeAP9KtAaTkIAuaEleYHSXeuKTn44Au3EDLLqMe6Ev//+cNNEAH8nW3+tTMycw+A+p+ORQRG0OUk3Zi/OAs8RLSL4l5JlcYj61zRsKf9nUPKjxduga38Am/JzIdmpCXvTc9CPTaT2URweBvPtxKSldBqOeCKTY0L01VXAuSUDSaLSTY7sNwCUHGLUuI2SLo2HZ6AX8mYroztaqLbD2GFprQSnFL8IyO6gf08EYBax5vWrLi0rBJX4T8kdfZNCofpQEEZcABeyvshcdTqxNyJnYnufQ3y/GL5IIDyjIQCQqt2ALujO6iX3ypWSNvWJ2WdokGd2yPHlA7E7BPEBM0CwI6X1Gswlz0SRyBvU7DMD3RaOr2yEegYPmJWokRdf2K0lzk1thzSP4TgR0tFZKaaTGz1ZPhO3b9wI6KQ7NQ0N89bbSQzwwAemNv/Mm8VfHZjKi0tDLtJjgsWe0jZBl4GnN59y+zxh/2uyisJOhIYTRUcRFmpIg3Fd3y6hp6tErTsstSs9z/APD0ZzCECCzLw2qqDDX2Dd2Ld0+dOxixA6QO7pkJ5Cr4st339C87F+PJYDc1VKMiT4BgmIowtPZGjtBg9q02UNKUt0k+z0HBdq0HFyVpWWNSbvAiPwZ8EYGcD1yR2kGyou2ceOnmV56hflIYpmH9K2kyQRc9WmC0BhPWJtP0AW2fvWaz2J6+/C5YXJXKMBxZiqZeIyu+sY9hJGmyEK9N9MOCpQhLVNvHxyVg0I1EgWy/UdPLnyglgKfkXcbbSqPUkFqqBJ+yr/3SZ3DtYWu7OX9ma18UNc7rej07uuWKHmfv26f33/K2Ild0FIzaL92IoPePhdTwdJBHsP9TlMW1qmdVpYXcBF+Kt4kYnlmJNmxyr9kcfesVzRUjGvoSSmYC+ZgTlvsxuGFLybynPscTG87/Tqsepdz9/Gx/ChXB2oonzHnMMQmwpJEb1BVtQrvwMzEopkWjLx4/QrWVJf0X+0cL5vO84eenGcaHw3Jy6euubF4k0eD
x-forefront-antispam-report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:DB9PR07MB7946.eurprd07.prod.outlook.com;PTR:;CAT:NONE;SFS:(13230040)(1800799024)(376014)(366016)(38070700021);DIR:OUT;SFP:1101;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: tu87+wyv0+NP5tw6Yd3/28/Nu4g1isrDF/s0yW9/FpMhpVE8yVEdeBRHlaQ9yRvkTLe6UvUVGlTNIB0PZxK5RnAuFlPmWz5vCmG+HM7oEbI63nthnQwEs8Zqu2NPhBXV0nBtJzYEW+hDUrUn8BSLFfvelc3BHwhS+QhDeiyOE1qXuxlLQnN3laaI/4vP9HJppolhWDfzC28Cts+HdBG3hSZuNLlic9x5qJ7luU2C+Cw0cEU+FPphGnog4dXtzYRK85gxHWNrK/0DK6ehsmHFnRct/DyUmwW/jj3T802c6NVP9QsINfaQAq2e24lrSLbDqPf085S3dlBof+FKYazGseePTG+dvsMq5OJN/Btks52lW4TRdC4c0Qac28Jr9cSNBKdiEoh1X01QJBI5dbaeo2MZiOTzAjfXF+DMYdf55GEBoWRVDaeoGPRzHg4JM4SFo2pmz0pyYzOGzrNLPIfMW+HJz4aB8bmtbw7PpoIUYcD6amdZHjIAfZeDskT5wG5mYpumCHz354DeRMOItH0ML/ofNGLkc9uK8UwC87kLQ1hc0L3/IB6xbBz5ZLp9Ko7KscFAdnAHxI+pCuuhGT1IETC7CmWr4b0JGOBBnW0ro1JHiAEe0LBIDOXDtfwlWzb/Aov4QmDOPJTuLzLcnN38esHz3W9AMbPLHbQ+vgpihFFHIH+8rkkWFoZX7tcVpwqutlGSyqIWO4UrOuvDJCazH+Jf3GJdtcRuXzc+Jzpsq2IeHfmJPVYthSA+R2KMjSLlRfRk2Fm7QzJszR/am566pca/xWqOxSDvHAxz1dMOEq6LxNj9JHFvqpZwpmQbzzRUTPAPYVdl0Sr5Eor8yuKPoyzyR/hrWAi5rs5tq+OnpZ3b+su6hUV+iX3BfHzYG3JRdSZEiQ5PIW1BjJRI9/j/Ofa6Nx3Rzo2z3PiG4LqEDDVuUWA4AzLh+8dCZFI9ZQ+MFoFb5/BdlHQ/V916y7Ce9fMC+m2Xp1fz74cK6sMgiDAOpM7ca442vySMa8KWMW5hyw+R7WS9IFYo9AhCNFkclBHtBy07D9YSnwhqx3QYpUpIIB3XxIt+OPlQi8INQs3dTdSTqoLMSJRWFmExCLdR1B6fAuLTSTvW7i8dkspJPZoOGRJaquPO6o/6/XhzfSeE25b8Sf2P0YxXNDSVu1F6AzfkQ/5aEttmtzY6xBfEUdeqV4y3r2QtII3lnGUz5qBwKp0WFuC1E5ObZcoeIv56rTqh+E6Uf1QnlmGDzl32i51rYsmg3yAgbo4utbYu49u5y4mTHUwEnpWnGi2CnxnWCcqZ5Aia23gVWo69aqoSl0WUYaDqjboU8xvcn2CG1BgOXrouphwb4YHnqMIdg1Os5QTCkGfzQtR4qz3Wo3fK/UY3tm2rTwfMpRi9NdLGFsO/UjfjMZHtOLQUmBBb1F7Ta3qYnbotTbgY1NKxYJK6fkxPz2Dq5Vda4zT+3RHiYfSFtceYaRRR32/WFsbn0W5CN78cEvgh9kjb0/fghBuWXj82wWcZPRxVsovObFismpoVGQCchs5uH/y8J03CGX31ju6Goo9z/NCoMv2fD0e4+FA=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DB9PR07MB7946.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 1a66fd08-b740-46d4-bf59-08de29c9ee7c
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Nov 2025 13:20:39.8956 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: OD3l3levOI7GgvS9bJ/T4wopglmmU7/J4DliyP4DvTocno8h7NnfSupE3rc0MR7D4n9nfxnQ2jSoWRjnbc9fuQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM8PR07MB7620
Message-ID-Hash: ICWN6KO64N2RRLK6OFV7NG2PZYSTOXEP
X-Message-ID-Hash: ICWN6KO64N2RRLK6OFV7NG2PZYSTOXEP
X-MailFrom: ietfc@btconnect.com
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: Keyur Patel <keyur@arrcus.com>, Sue <skh@ndzh.com>, "draft-ietf-idr-bgp-model@ietf.org" <draft-ietf-idr-bgp-model@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Idr] Re: New Liaison Statement, "oLS to IETF on BGP data model"
List-Id: Inter-Domain Routing <idr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/V41on_REzY2D-M7aqxSrMRR_88U>
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>

From: Ketan Talaulikar <ketant.ietf@gmail.com>
Sent: 22 November 2025 07:25

< trimming the list >

Hello All,

The BGP-4 YANG model document has gone through WGLC and has been waiting for implementations for more than 2 years now. I am not sure of its current status - I do see warnings and errors being reported on the YANG.

All 3 IDR chairs are authors on it and the IDR Secretary is the document shepherd. I recognize this odd situation. However, a decision on the future of this document is now overdue. This Liaison is a good trigger for the WG to make a decision (and within a timeframe so the Liaison can be responded to).

As AD, I've already expressed my view that an exception to the 2 implementation rule be sought from the WG for this document so it can be published as an RFC. I believe it was in Madrid where I had expressed that view, but perhaps even before that. If there is consensus to proceed with that exception, this can be progressed - else it just stays waiting for implementation and the WG will need to give a suitable response to BBF.

Sue, Jeff, Keyur, and Jie, could you please take this topic up as a priority request from me for discussion at your next meeting? Please let the WG know your thoughts and if there is anything that you would like me to do, please let me know.

<tp>

I was involved with BGP4 and with SNMP Network Management in the years preceding RFC4271 and expected - hoped for - a management RFC to appear soon after.  Since then, I have formed the opinion that there is not enough commonality across implementations for an IETF management model and see the lack of progress with the data model as a symptom of that.  If the I-D does progress, then I think that it needs a clear statement up front about the lack of consensus across implementations of a management model; or we could have models that are not Standards Track that reflect the approach taken by one, or a few, of the implementations.  I do not have a view as to which implementations of network management are most suitable -  I no longer have the exposure I had in the days of producing RFC4271. 

It may just be that the world of network management has moved on and an SNMP BGP model from the IETF .is no longer appropriate.

Tom Petch

Thanks,
Ketan


On Sat, Nov 22, 2025 at 8:09 AM Liaison Statement Management Tool <statements@ietf.org<mailto:statements@ietf.org>> wrote:
Title: oLS to IETF on BGP data model
Submission Date: 2025-11-21
URL of the IETF Web page: https://datatracker.ietf.org/liaison/2081/

To: Inter-Domain Routing (idr)
From: Broadband Forum
Purpose: For information


Email Addresses
---------------
From: lylavoie@iol.unh.edu<mailto:lylavoie@iol.unh.edu>
To: Sue <skh@ndzh.com<mailto:skh@ndzh.com>>,Keyur Patel <keyur@arrcus.com<mailto:keyur@arrcus.com>>,Jeffrey Haas <jhaas@pfrc.org<mailto:jhaas@pfrc.org>>
Cc: Jeffrey Haas <jhaas@pfrc.org<mailto:jhaas@pfrc.org>>,Inter-Domain Routing Discussion List <idr@ietf.org<mailto:idr@ietf.org>>,Keyur Patel <keyur@arrcus.com<mailto:keyur@arrcus.com>>,Xueyan Song <song.xueyan2@zte.com.cn<mailto:song.xueyan2@zte.com.cn>>,Jim Guichard <james.n.guichard@futurewei.com<mailto:james.n.guichard@futurewei.com>>,Ketan Talaulikar <ketant.ietf@gmail.com<mailto:ketant.ietf@gmail.com>>,Sue <skh@ndzh.com<mailto:skh@ndzh.com>>,Gunter Van de Velde <gunter.van_de_velde@nokia.com<mailto:gunter.van_de_velde@nokia.com>>,Craig Thomas <cthomas@broadband-forum.org<mailto:cthomas@broadband-forum.org>>,Karina Rocha-Gabbard <krocha@broadband-forum.org<mailto:krocha@broadband-forum.org>>,Bruno Cornaglia <bruno.cornaglia@vodafone.com<mailto:bruno.cornaglia@vodafone.com>>,Mengmeng Li <limengmeng@chinamobile.com<mailto:limengmeng@chinamobile.com>>,Haomian Zheng <zhenghaomian@huawei.com<mailto:zhenghaomian@huawei.com>>
Response Contacts: lylavoie@iol.unh.edu<mailto:lylavoie@iol.unh.edu>
Technical Contacts:


Body: Dear Colleagues,

Broadband Forum is currently working on defining protocols, message flows and data models for disaggregated devices. In particular, Provider Cloud Work Area is working on Disaggregated Access Node, namely TR-477, and in the second release of it, currently on draft, it is focusing on the disaggregation of L3 functions. Obviously, apart from creating the CP-UP message flows for the disaggregated functions, BBF is not developing any new data models, if they already exist in other SDOs. One of the L3 functions currently under development is BGP and BBF is reusing the current draft data model developed by IETF:

•       draft-ietf-idr-bgp-model-18
link: draft-ietf-idr-bgp-model-18 - YANG Model for Border Gateway Protocol (BGP-4)

of which we are only using the following data model: ietf-bgp@2024-10-21.yang.

The BBF document referring to this data model (WT-477i2) is almost completed, and we are going to proceed with our straw ballot process. Anyhow we cannot proceed with the publication until the IETF data model on BGP is published.

So, we would like to ask if the IETF have any target publication dates for the data model mentioned above in order to understand when we can publish the issue 2 of TR-477.


Sincerely,

Lincoln Lavoie,
Broadband Forum Technical Committee Chair


CC:
Liaisons at BBF <liaisons@broadband-forum.org<mailto:liaisons@broadband-forum.org>>
Lincoln Lavoie, Broadband Forum Technical Committee Chair <lylavoie@iol.unh.edu<mailto:lylavoie@iol.unh.edu>>
Craig Thomas, Broadband Forum Managing Director <cthomas@broadband-forum.org<mailto:cthomas@broadband-forum.org>>
Karina Rocha-Gabbard, Broadband Forum Member Operations and Support Manager <krocha@broadband-forum.org<mailto:krocha@broadband-forum.org>>
Bruno Cornaglia, Broadband Forum Provider Cloud Work Area co-Director <bruno.cornaglia@vodafone.com<mailto:bruno.cornaglia@vodafone.com>>
Mengmeng Li, Broadband Forum Provider Cloud Work Area co-Director <limengmeng@chinamobile.com<mailto:limengmeng@chinamobile.com>>
Haomian Zheng, Broadband Forum Provider Cloud Work Area co-Director <zhenghaomian@huawei.com<mailto:zhenghaomian@huawei.com>>
statements@ietf.org<mailto:statements@ietf.org>
bbf-liaison@ietf.org<mailto:bbf-liaison@ietf.org>
Attachments:

    LIAISE-719
    https://www.ietf.org/lib/dt/documents/LIAISON/liaison-2025-11-22-broadband-forum-idr-ols-to-ietf-on-bgp-data-model-attachment-1.docx