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

Ketan Talaulikar <ketant.ietf@gmail.com> Sat, 22 November 2025 07:25 UTC

Return-Path: <ketant.ietf@gmail.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 3B8CC8E83D50 for <idr@mail2.ietf.org>; Fri, 21 Nov 2025 23:25:58 -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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=gmail.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 bYAL3stcjJIC for <idr@mail2.ietf.org>; Fri, 21 Nov 2025 23:25:57 -0800 (PST)
Received: from mail-pl1-x633.google.com (mail-pl1-x633.google.com [IPv6:2607:f8b0:4864:20::633]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 787338E83D49 for <idr@ietf.org>; Fri, 21 Nov 2025 23:25:57 -0800 (PST)
Received: by mail-pl1-x633.google.com with SMTP id d9443c01a7336-299d40b0845so43925015ad.3 for <idr@ietf.org>; Fri, 21 Nov 2025 23:25:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1763796356; x=1764401156; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=j+sCijGQSc9HBk4Dw5pmdpbmu45gNppqnCwlFYMptT8=; b=Fdue1mTN/twLcwbardV1BHKxLeS6xcPMDGD50umPbxAhWbs34zVriennqAfhznOGIB yHshj11HUOJFm4EM0R5JREAJMiywgwXi7H3gz6Cmr8QI0jvMyiwwmuKcMniSBoPaQBdM ZIDNnAs7MZJLcijb2NFBrPTFodETBDtFtTUxrzUP/Ie2rn4H2huqM1trad36co4HfN0J IOVLEiDtKyWhuKhW0V66DcMxwlbEJgTjGBD0n7ZBZpACwKbrfbey+eQHzcL2vara2ask e+77k9GAcBj6KmGmAUklVmvQ+3t2MDHJTjslnt6ZROq/IVFerqT8gwK3wN0TYJRM4gBQ qVwg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1763796356; x=1764401156; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=j+sCijGQSc9HBk4Dw5pmdpbmu45gNppqnCwlFYMptT8=; b=tbY5cEVPbQfRcvYhod9TVX7DGg6FSFTQVbs1gskDlgHi8AthKq8AXqX1MI0sCVDnBL 5DCfai73yTScjDMC8AEWwdb47JIyK52wp0oIUBG/YpLqaGBWOXHl06VgZmzWnx+jlsBM P+2fSLqtwUhv5GbE2IFcvCiVRqx22NhY8/srv8myOLxI+DxwnD4AidkdjT+PCscny3nX Sjfmk7IRZQjT2AQPpF65a5nzjuK2GP0MgohM5ypisvjD8qBwRvsM+XxRDfLg4Te5cc3h WPI9mcRD1ommMUhqehjQ02kbH9meZhu2nxBA9yYJfKdS8HQVLJHSSWICzcz7S2wBVJa+ S+cw==
X-Gm-Message-State: AOJu0Yy5u4UiSS+HgCtqhcOUBGqj+kogNUig6Gdx5mhW0vosc0ctbosg IhxUbS7qq1ChDAzlte4aB2odBW7n02y0xvJwARh1ZsIgSWpgTIUvvB9jGnp/PDI3RxGxstS6gRd hBdr4u2c30k9/5IDIg8PWw8/6JCPshI+eKg==
X-Gm-Gg: ASbGncuQ/X0bGPZliwWq1fmATpxUHyxTtnyhWIQBsSuol7ClmF9X35a4FQXFUSir5aL fia1M+prpqnumg3iXrbrMUCBeqk7MXyhHyQWR0T0zuecd91w6Br+McLT/DjAF81st3oGGjgB5Mv ln8GMZCLvLAZNVpZ827lAFPMpxsBJ82oIedhh7Pt3cg109BJMpt/aJEeaEalXDqX9A3Ikbdb0D+ Ne0amE6QQbb4QArhnaN3PyhOI0+a8e2g2mRvbNpMgUgFF8nS7GVMM6YvKvhciqhP+IOEHcKvF/H bl+2gCNdmb7WkLUGBIE4VmObJGmV
X-Google-Smtp-Source: AGHT+IHSMy3fc8WxRlwX9qsL/vcVFLHQPrCvJgaRDiuy1kfpaC5qcon0DIxGu7vZuF3HIEkPO5fBlpzVDOuI9H8uWp4=
X-Received: by 2002:a17:903:2ca:b0:295:7f1d:b034 with SMTP id d9443c01a7336-29b6be76b91mr69067005ad.4.1763796356075; Fri, 21 Nov 2025 23:25:56 -0800 (PST)
MIME-Version: 1.0
References: <176377917609.1807088.18231834189018308158@dt-datatracker-5bd94c585b-wk4l4>
In-Reply-To: <176377917609.1807088.18231834189018308158@dt-datatracker-5bd94c585b-wk4l4>
From: Ketan Talaulikar <ketant.ietf@gmail.com>
Date: Sat, 22 Nov 2025 12:55:43 +0530
X-Gm-Features: AWmQ_bnDswh2nlX3Vn5A4UDdUIErBnjAXu_0TitzwNWhy8zDHGQRpC9Qb9p3CcU
Message-ID: <CAH6gdPwpL59w6tPxvTqbExUExRYotSETQFt3sFJwGdNEr47y2w@mail.gmail.com>
To: Inter-Domain Routing Discussion List <idr@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000429560064429d7ea"
Message-ID-Hash: QN5LUGRQEE6RIITZSMWBRDUQB623FXGX
X-Message-ID-Hash: QN5LUGRQEE6RIITZSMWBRDUQB623FXGX
X-MailFrom: ketant.ietf@gmail.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
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/Cyw74yTKXEGLTOXcHCKU1TEPlRw>
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>

< 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
>
>
>