[Idr] Re: New Liaison Statement, "oLS to IETF on BGP data model"
Adrian Farrel <adrian@olddog.co.uk> Sat, 22 November 2025 16:25 UTC
Return-Path: <adrian@olddog.co.uk>
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 1E66F8EA99BF; Sat, 22 Nov 2025 08:25:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.697
X-Spam-Level:
X-Spam-Status: No, score=-2.697 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, MIME_HTML_ONLY=0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, 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=olddog.co.uk
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 sxTB_VT6x9lK; Sat, 22 Nov 2025 08:25:30 -0800 (PST)
Received: from mta7.iomartmail.com (mta7.iomartmail.com [62.128.193.157]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 35E248EA99B4; Sat, 22 Nov 2025 08:25:30 -0800 (PST)
Received: from vs2.iomartmail.com (vs2.iomartmail.com [10.12.10.123]) by mta7.iomartmail.com (8.14.7/8.14.7) with ESMTP id 5AMGPJDc006597; Sat, 22 Nov 2025 16:25:19 GMT
Received: from vs2.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 64D574604B; Sat, 22 Nov 2025 16:25:18 +0000 (GMT)
Received: from vs2.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 4EDF746048; Sat, 22 Nov 2025 16:25:18 +0000 (GMT)
Received: from asmtp2.iomartmail.com (unknown [10.12.10.249]) by vs2.iomartmail.com (Postfix) with ESMTPS; Sat, 22 Nov 2025 16:25:18 +0000 (GMT)
Received: from ioxnode2.iomartmail.com (ioxnode2.iomartmail.com [10.12.10.69]) (authenticated bits=0) by asmtp2.iomartmail.com (8.14.7/8.14.7) with ESMTP id 5AMGPHtC012089 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 22 Nov 2025 16:25:17 GMT
Date: Sat, 22 Nov 2025 16:25:17 +0000
From: Adrian Farrel <adrian@olddog.co.uk>
To: Ketan Talaulikar <ketant.ietf@gmail.com>, Inter-Domain Routing Discussion List <idr@ietf.org>
Message-ID: <147777621.51329.1763828717874@www.getmymail.co.uk>
In-Reply-To: <CAH6gdPwpL59w6tPxvTqbExUExRYotSETQFt3sFJwGdNEr47y2w@mail.gmail.com>
References: <176377917609.1807088.18231834189018308158@dt-datatracker-5bd94c585b-wk4l4> <CAH6gdPwpL59w6tPxvTqbExUExRYotSETQFt3sFJwGdNEr47y2w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
Importance: Normal
X-Mailer: Open-Xchange Mailer v7.10.6-Rev75
X-Originating-IP: 148.252.145.170
X-Originating-Client: open-xchange-appsuite
X-Thinkmail-Auth: adrian@olddog.co.uk
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=olddog.co.uk; h=date :from:to:cc:message-id:in-reply-to:references:subject :mime-version:content-type:content-transfer-encoding; s= 20221128; bh=OprOSNcBuQgsj16r2d15coC4fVEPmFK0UOvGGteVxvY=; b=MdN oOW3Ka0BEixHoJeDpnspvrc/YNlLYr94p9bCmHUuuBG8pqbyXuBhx3MjcPXIGG0N Zhqnm+FOSaht86gwxd18Ie3vAS6xiDcTGcidDxN0FSGmn9tEx3qheatIhk77jx+8 GrZ1RWIWrjZfRh0nv1JIFnwweF4JkuIZWiKL6xqE9OuGQJS2twajBwGXVFi3ruN3 zt0yu0w1dkDpwgu912wYHCfSIOei1/QSmZsr1kNkTUd60E2yirpWuZ8azEQFiM/G nJMxMmSz4TtgvQSzGwI7J3nW9BriWAr1BNk4vwmDIP7wpsofKrfuqpkohn42+66y wquxiVJHWfi8fVzKpfA==
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.1.0.2090-9.0.0.1006-29464.005
X-TM-AS-Result: No--28.791-10.0-31-10
X-imss-scan-details: No--28.791-10.0-31-10
X-TMASE-Version: IMSVA-9.1.0.2090-9.0.1006-29464.005
X-TMASE-Result: 10--28.791000-10.000000
X-TMASE-MatchedRID: gTucSmrmRMOnvGCyBToTI8G0UNgaZpYqnSd2cRY8xQNWcVQdwdqmz45h luopTaWkbSL9AN4UjltdGdXpDccA9EtHpMdfrXMK1sYhnIFjUPWk8yaNAmZfIQX+uAQWEHBwIvF faOl5ZuwXeXyQhMh1L1/jverGs3tKrguQkHuVB6zw62PQq99HWeWzJnTmLPxv9HT9F00qW4Bgzs KpSuFS76VPEswngkIv30lz0YgK/LdyxXyvOO81YrxygpRxo4699v33UW8WNYDJVWdgKXnqZLO7S tVQmHFETQPMqkJM2T5fLcn0UlqnqMdu3RKeXyS0nVTWWiNp+v+6tA46y8NPI/pjJBhMwHdy1HfW kIip/loal4b0i7QFghFHcsbpC3Q6hrQySeID7N/HV2LNfYpGE8Jd4cnAlxP2d1fgNR/swoi20nP Q2eZ7CSV5FjRCWGfo7g6B4WJLTOXxtRHCfVBMec3WPbtc5QfmKQNhMboqZlq15eNIExieaeEmS2 TKncvxGL6ebLY9oAxgP/rzjYxQI0MgJ2KtiHoavf5DDPstHFGjy03X2hNeV9Z5C2tydwt9Q0rE1 8rDtKKEm1sE8Ofsmz5/8piHpDboTZAoN+FvjgeNyH/G92IcfCJIyemE7blFXmT0khWg2nbdKUSB W7I322I6NVF4O0dzgF/gZnNr7fDyIohFuDqYop4CIKY/Hg3AWQy9YC5qGvy2s0ar5ZAS9MdwGuK Im8sZ7DhbMHwWXCRRzX47Vf0DMQ==
X-TMASE-SNAP-Result: 1.821001.0001-0-1-22:0,33:0,34:0-0
Message-ID-Hash: 32L6RE4AQDPJNXEMMLHACPMPASKHFOYK
X-Message-ID-Hash: 32L6RE4AQDPJNXEMMLHACPMPASKHFOYK
X-MailFrom: adrian@olddog.co.uk
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
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/y8SiqRqAJhTtY-S5kadXGrz6fFc>
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>
On 22/11/2025 07:25 GMT Ketan Talaulikar <ketant.ietf@gmail.com> wrote:< 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.Thanks,Ketan
_______________________________________________On Sat, Nov 22, 2025 at 8:09 AM Liaison Statement Management Tool <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/" target="_blank" rel="noopener nofollow">https://datatracker.ietf.org/liaison/2081/
To: Inter-Domain Routing (idr)
From: Broadband Forum
Purpose: For information
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:
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>
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:
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" target="_blank" rel="noopener nofollow">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
Idr mailing list -- idr@ietf.org
To unsubscribe send an email to idr-leave@ietf.org
- [Idr] New Liaison Statement, "oLS to IETF on BGP … Liaison Statement Management Tool
- [Idr] Re: New Liaison Statement, "oLS to IETF on … Ketan Talaulikar
- [Idr] Re: New Liaison Statement, "oLS to IETF on … tom petch
- [Idr] Re: New Liaison Statement, "oLS to IETF on … Adrian Farrel
- [Idr] Re: New Liaison Statement, "oLS to IETF on … song.xueyan2
- [Idr] Re: New Liaison Statement, "oLS to IETF on … Jeffrey Haas
- [Idr] Re: New Liaison Statement, "oLS to IETF on … Jeffrey Haas
- [Idr] Re: New Liaison Statement, "oLS to IETF on … Ketan Talaulikar
- [Idr] Re: New Liaison Statement, "oLS to IETF on … mohamed.boucadair
- [Idr] Re: New Liaison Statement, "oLS to IETF on … Mahesh Jethanandani
- [Idr] Re: New Liaison Statement, "oLS to IETF on … Jeffrey Haas
- [Idr] Re: New Liaison Statement, "oLS to IETF on … song.xueyan2
- [Idr] Re: New Liaison Statement, "oLS to IETF on … mohamed.boucadair
- [Idr] Re: New Liaison Statement, "oLS to IETF on … Jeffrey Haas
- [Idr] Re: New Liaison Statement, "oLS to IETF on … song.xueyan2