[Idr] Re: New Liaison Statement, "oLS to IETF on BGP data model"
song.xueyan2@zte.com.cn Mon, 24 November 2025 02:59 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 157EB8F46F08; Sun, 23 Nov 2025 18:59:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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=ham 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 e6ubPQrpfWbb; Sun, 23 Nov 2025 18:59:54 -0800 (PST)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [160.30.148.35]) (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 07B8A8F46F01; Sun, 23 Nov 2025 18:59:53 -0800 (PST)
Received: from mse-fl2.zte.com.cn (unknown [10.5.228.133]) (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 mxhk.zte.com.cn (FangMail) with ESMTPS id 4dF9Xd0653z8Xs70; Mon, 24 Nov 2025 10:59:45 +0800 (CST)
Received: from njy2app03.zte.com.cn ([10.40.13.14]) by mse-fl2.zte.com.cn with SMTP id 5AO2vsWs092934; Mon, 24 Nov 2025 10:59:13 +0800 (+08) (envelope-from song.xueyan2@zte.com.cn)
Received: from mapi (njy2app03[null]) by mapi (Zmail) with MAPI id mid203; Mon, 24 Nov 2025 10:59:14 +0800 (CST)
Date: Mon, 24 Nov 2025 10:59:14 +0800
X-Zmail-TransId: 2afb6923ca0214d-0f06c
X-Mailer: Zmail v1.0
Message-ID: <20251124105914161ca6etQmSGsv5vTUfIrZW6@zte.com.cn>
In-Reply-To: <147777621.51329.1763828717874@www.getmymail.co.uk>
References: 176377917609.1807088.18231834189018308158@dt-datatracker-5bd94c585b-wk4l4,CAH6gdPwpL59w6tPxvTqbExUExRYotSETQFt3sFJwGdNEr47y2w@mail.gmail.com,147777621.51329.1763828717874@www.getmymail.co.uk
Mime-Version: 1.0
From: song.xueyan2@zte.com.cn
To: adrian@olddog.co.uk
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl2.zte.com.cn 5AO2vsWs092934
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.133 unknown Mon, 24 Nov 2025 10:59:45 +0800
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 6923CA21.000/4dF9Xd0653z8Xs70
Message-ID-Hash: DBDE5ZTNYZO4LQ25RSTR2T7YQS2OIK3O
X-Message-ID-Hash: DBDE5ZTNYZO4LQ25RSTR2T7YQS2OIK3O
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: idr@ietf.org, keyur@arrcus.com, 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/MqQk5E7_-mqtSurc7qUXt_Ih_zg>
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 Adrian and all, Yes, it would be mutually beneficial for BBF provide implementation information to IETF. I am currently discussing this with BBF leadership to identify member companies who have deployed the bgp data model. If any implementations are found (we hope so), I will encourage them to share their information directly with IETF IDR or provide it through a follow-up liaison. Will keep you updated on any progress. Best regards, Xueyan (BBF Liaison Manager) Original From: AdrianFarrel <adrian@olddog.co.uk> To: Ketan Talaulikar <ketant.ietf@gmail.com>;Inter-Domain Routing Discussion List <idr@ietf.org>; Cc: Keyur Patel <keyur@arrcus.com>;Sue <skh@ndzh.com>;draft-ietf-idr-bgp-model@ietf.org <draft-ietf-idr-bgp-model@ietf.org>; Date: 2025年11月23日 00:26 Subject: [Idr] Re: New Liaison Statement, "oLS to IETF on BGP data model" I woner whether the BBF, being all enthusiastic, could supply us with any implementation information. (Obviously, fixing the YANG is important for us and the BBF.) A 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/ 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 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