Return-Path: <jhaas@pfrc.org>
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 786E7942913C;
	Tue,  2 Dec 2025 12:41:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5
	tests=[BAYES_00=-1.9, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001,
	RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001]
	autolearn=unavailable autolearn_force=no
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 wE7CZyYYO0vC; Tue,  2 Dec 2025 12:41:41 -0800 (PST)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108])
	by mail2.ietf.org (Postfix) with ESMTP id 4CD4A94282AC;
	Tue,  2 Dec 2025 12:33:29 -0800 (PST)
Received: from smtpclient.apple (99-188-202-8.lightspeed.livnmi.sbcglobal.net
 [99.188.202.8])
	by slice.pfrc.org (Postfix) with ESMTPSA id A665D1E24F;
	Tue,  2 Dec 2025 15:33:28 -0500 (EST)
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.10\))
From: Jeffrey Haas <jhaas@pfrc.org>
In-Reply-To: 
 <176377917609.1807088.18231834189018308158@dt-datatracker-5bd94c585b-wk4l4>
Date: Tue, 2 Dec 2025 15:33:28 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <3595371A-9DA2-48DD-A43F-D699D9270FC2@pfrc.org>
References: 
 <176377917609.1807088.18231834189018308158@dt-datatracker-5bd94c585b-wk4l4>
To: Liaison Statement Management Tool <statements@ietf.org>
X-Mailer: Apple Mail (2.3696.120.41.1.10)
Message-ID-Hash: EGRAWNLVNBTHGMOYHYY7NUQN6CKBKB7V
X-Message-ID-Hash: EGRAWNLVNBTHGMOYHYY7NUQN6CKBKB7V
X-MailFrom: jhaas@pfrc.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: Keyur Patel <keyur@arrcus.com>, Sue <skh@ndzh.com>,
 Bruno Cornaglia <bruno.cornaglia@vodafone.com>,
 Craig Thomas <cthomas@broadband-forum.org>,
 Gunter Van de Velde <gunter.van_de_velde@nokia.com>,
 Haomian Zheng <zhenghaomian@huawei.com>,
 Inter-Domain Routing Discussion List <idr@ietf.org>,
 Karina Rocha-Gabbard <krocha@broadband-forum.org>,
 Mengmeng Li <limengmeng@chinamobile.com>, liaison-coordination@iab.org,
 lylavoie@iol.unh.edu
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: =?utf-8?q?=5BIdr=5D_Re=3A_New_Liaison_Statement=2C_=22oLS_to_IETF_on_BGP_dat?=
	=?utf-8?q?a_model=22?=
List-Id: Inter-Domain Routing <idr.ietf.org>
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/idr/iWNmqpyWsUF8LHrISIpF_mcyexQ>
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>

Lincoln,

Thank you for inquiry into the IETF BGP YANG model.  A more complete =
response to the Broadband Forum's liaison statement should be =
forthcoming in the next few days after the IDR Chairs convene to discuss =
the question.

To assist the IETF IDR Working Group's participants and chairs in =
answering your question, it would be helpful to have further details =
relating to the BBF data model that has dependencies on the IETF BGP =
YANG data model.  This is the WT-477i2 cited below. =20

The BGP YANG internet-draft is composed of multiple YANG modules. If the =
BBF could help make WT-477i2 available for for review, this will assist =
IDR in determining what portions of the IETF work is most critical to =
satisfy the dependencies that the BBF has on the IETF work. =20

Regards,

Jeffrey Haas, IDR Co-Chair.

> On Nov 21, 2025, at 9:39 PM, Liaison Statement Management Tool =
<statements@ietf.org> wrote:
>=20
> 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/
>=20
> To: Inter-Domain Routing (idr)
> From: Broadband Forum
> Purpose: For information
>=20
>=20
> Email Addresses
> ---------------
> From: lylavoie@iol.unh.edu
> To: Sue <skh@ndzh.com>,Keyur Patel <keyur@arrcus.com>,Jeffrey Haas =
<jhaas@pfrc.org>
> Cc: Jeffrey Haas <jhaas@pfrc.org>,Inter-Domain Routing Discussion List =
<idr@ietf.org>,Keyur Patel <keyur@arrcus.com>,Xueyan Song =
<song.xueyan2@zte.com.cn>,Jim Guichard =
<james.n.guichard@futurewei.com>,Ketan Talaulikar =
<ketant.ietf@gmail.com>,Sue <skh@ndzh.com>,Gunter Van de Velde =
<gunter.van_de_velde@nokia.com>,Craig Thomas =
<cthomas@broadband-forum.org>,Karina Rocha-Gabbard =
<krocha@broadband-forum.org>,Bruno Cornaglia =
<bruno.cornaglia@vodafone.com>,Mengmeng Li =
<limengmeng@chinamobile.com>,Haomian Zheng <zhenghaomian@huawei.com>
> Response Contacts: lylavoie@iol.unh.edu
> Technical Contacts:=20
>=20
>=20
> Body: Dear Colleagues,
>=20
> 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:
>=20
> =E2=80=A2	draft-ietf-idr-bgp-model-18
> link: draft-ietf-idr-bgp-model-18 - YANG Model for Border Gateway =
Protocol (BGP-4)
>=20
> of which we are only using the following data model: =
ietf-bgp@2024-10-21.yang.
>=20
> 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.
>=20
> 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.
>=20
>=20
> Sincerely,
>=20
> Lincoln Lavoie,
> Broadband Forum Technical Committee Chair
>=20
>=20
> CC:
> Liaisons at BBF <liaisons@broadband-forum.org>=20
> Lincoln Lavoie, Broadband Forum Technical Committee Chair =
<lylavoie@iol.unh.edu>
> Craig Thomas, Broadband Forum Managing Director =
<cthomas@broadband-forum.org>
> Karina Rocha-Gabbard, Broadband Forum Member Operations and Support =
Manager <krocha@broadband-forum.org>
> Bruno Cornaglia, Broadband Forum Provider Cloud Work Area co-Director =
<bruno.cornaglia@vodafone.com>
> Mengmeng Li, Broadband Forum Provider Cloud Work Area co-Director =
<limengmeng@chinamobile.com>
> Haomian Zheng, Broadband Forum Provider Cloud Work Area co-Director =
<zhenghaomian@huawei.com>
> statements@ietf.org
> bbf-liaison@ietf.org
> Attachments:
>=20
>    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
>=20

