[Idr] Re: New Liaison Statement, "oLS to IETF on BGP data model"
song.xueyan2@zte.com.cn Fri, 05 December 2025 01:58 UTC
Return-Path: <song.xueyan2@zte.com.cn>
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 9B85295BF327; Thu, 4 Dec 2025 17:58:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -0.859
X-Spam-Level:
X-Spam-Status: No, score=-0.859 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_PBL=3.335, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no 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 KsZzjAsXhiGR; Thu, 4 Dec 2025 17:58:32 -0800 (PST)
Received: from mxct.zte.com.cn (mxct.zte.com.cn [183.62.165.209]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 079CD95BF317; Thu, 4 Dec 2025 17:58:30 -0800 (PST)
Received: from mse-fl1.zte.com.cn (unknown [10.5.228.132]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mxct.zte.com.cn (FangMail) with ESMTPS id 4dMvfh61wtz501bV; Fri, 05 Dec 2025 09:58:20 +0800 (CST)
Received: from njb2app07.zte.com.cn ([10.55.22.95]) by mse-fl1.zte.com.cn with SMTP id 5B51wAJQ022023; Fri, 5 Dec 2025 09:58:10 +0800 (+08) (envelope-from song.xueyan2@zte.com.cn)
Received: from mapi (njy2app02[null]) by mapi (Zmail) with MAPI id mid203; Fri, 5 Dec 2025 09:58:11 +0800 (CST)
Date: Fri, 05 Dec 2025 09:58:11 +0800
X-Zmail-TransId: 2afa69323c333e1-20ee3
X-Mailer: Zmail v1.0
Message-ID: <20251205095811579j2VopoxzIMNxVKGJCruZ9@zte.com.cn>
In-Reply-To: <3595371A-9DA2-48DD-A43F-D699D9270FC2@pfrc.org>
References: 176377917609.1807088.18231834189018308158@dt-datatracker-5bd94c585b-wk4l4,3595371A-9DA2-48DD-A43F-D699D9270FC2@pfrc.org
Mime-Version: 1.0
From: song.xueyan2@zte.com.cn
To: jhaas@pfrc.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl1.zte.com.cn 5B51wAJQ022023
X-TLS: YES
X-SPF-DOMAIN: zte.com.cn
X-ENVELOPE-SENDER: song.xueyan2@zte.com.cn
X-SPF: None
X-SOURCE-IP: 10.5.228.132 unknown Fri, 05 Dec 2025 09:58:20 +0800
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 69323C3C.000/4dMvfh61wtz501bV
Message-ID-Hash: 2UGNA3DJMZ6UZHXY3AAJAVFWXFMSDEEZ
X-Message-ID-Hash: 2UGNA3DJMZ6UZHXY3AAJAVFWXFMSDEEZ
X-MailFrom: song.xueyan2@zte.com.cn
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: statements@ietf.org, keyur@arrcus.com, skh@ndzh.com, bruno.cornaglia@vodafone.com, cthomas@broadband-forum.org, gunter.van_de_velde@nokia.com, zhenghaomian@huawei.com, idr@ietf.org, krocha@broadband-forum.org, limengmeng@chinamobile.com, liaison-coordination@iab.org, lylavoie@iol.unh.edu
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/S0XI4YyQFH6RAeTtdpMafGwHQWc>
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 Jeff, all Thank you for the response and for sharing the plan regarding the liaison response to BBF. As mentioned in the liaison, the BBF YANG data model is fully depend on ietf-bgp@2024-10-21.yang and its dependencies. The further details of these dependencies, along with the relevant design aspects and working text of WT-477i2, will be provided in a follow-up liaison from BBF. The follow-up liaison will be discussed at our weekly meeting next week and will be sent shortly upon approval. We look forward to your further response and are ready to provide any additional details if needed. Best regards, Xueyan Song BBF-IETF Liaison Officer, Broadband Forum Original From: JeffreyHaas <jhaas@pfrc.org> To: Liaison Statement Management Tool <statements@ietf.org>; 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>;Jim Guichard <james.n.guichard@futurewei.com>;Karina Rocha-Gabbard <krocha@broadband-forum.org>;Ketan Talaulikar <ketant.ietf@gmail.com>;Mengmeng Li <limengmeng@chinamobile.com>;宋雪雁00038118;liaison-coordination@iab.org <liaison-coordination@iab.org>;lylavoie@iol.unh.edu <lylavoie@iol.unh.edu>; Date: 2025年12月03日 04:33 Subject: Re: New Liaison Statement, "oLS to IETF on BGP data model" 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. 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. Regards, Jeffrey Haas, IDR Co-Chair. > On Nov 21, 2025, at 9:39 PM, 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/ > > 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 >
- [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