WG Action: Rechartered Global Routing Operations (grow)
The IESG <iesg-secretary@ietf.org> Fri, 09 May 2025 16:50 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@mail2.ietf.org
Received: from [10.244.8.181] (unknown [104.131.183.230]) by mail2.ietf.org (Postfix) with ESMTP id 067A626EACB8; Fri, 9 May 2025 09:50:53 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: WG Action: Rechartered Global Routing Operations (grow)
X-Test-IDTracker: no
X-IETF-IDTracker: 12.39.2
Auto-Submitted: auto-generated
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <174680945289.1288330.11973442637242180531@dt-datatracker-58d4498dbd-6gzjf>
Date: Fri, 09 May 2025 09:50:52 -0700
Message-ID-Hash: C2K7ZDADQGUTC5HYYBTKMTUZVSJDINCG
X-Message-ID-Hash: C2K7ZDADQGUTC5HYYBTKMTUZVSJDINCG
X-MailFrom: iesg-secretary@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: The IESG <iesg@ietf.org>, grow-chairs@ietf.org, grow@ietf.org
X-Mailman-Version: 3.3.9rc6
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/wx9WBSgKgK6NE2kqRmXm6Es7ozc>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>
The Global Routing Operations (grow) WG in the Operations and Management Area of the IETF has been rechartered. For additional information, please contact the Area Directors or the WG Chairs. Global Routing Operations (grow) ----------------------------------------------------------------------- Current status: Active WG Chairs: Job Snijders <job@sobornost.net> Paolo Lucente <paolo@ntt.net> Assigned Area Director: Mohamed Boucadair <mohamed.boucadair@orange.com> Operations and Management Area Directors: Mahesh Jethanandani <mjethanandani@gmail.com> Mohamed Boucadair <mohamed.boucadair@orange.com> Technical advisors: Jeffrey Haas <jhaas@pfrc.org> Mailing list: Address: grow@ietf.org To subscribe: https://www.ietf.org/mailman/listinfo/grow Archive: https://mailarchive.ietf.org/arch/browse/grow/ Group page: https://datatracker.ietf.org/group/grow/ Charter: https://datatracker.ietf.org/doc/charter-ietf-grow/ The Border Gateway Protocol (BGP) is fundamental to the operation of the global IP routing system and ensuring global reachability on the Internet. The purpose of the GROW working group is to consider the operational challenges associated with the global IP routing system (both IPv4 and IPv6), including but not limited to default-free zone routing table growth, forwarding tables growth, effects of the interactions between interior and exterior routing protocols, and effects of IPv4/IPv6 address allocation policies on the global routing system. The working group will document the operational aspects of measurement, monitoring, policy, operational global routing system security, or safe default behavior of global IP routing protocol implementations and deployments. The GROW working group will also develop and increase awareness to mitigations to prevent malpractice (e.g., route leaks) in the global routing system. The GROW working group will develop data models and building blocks for automating the operation of the global routing system. The GROW working group will collaborate with other working groups, primarily IDR working group, that are developing solutions for the global IP routing system. When solicited, the working group will review the solutions being developed for the global routing system by these other working groups and provide inputs related to operational implications. The working group will also provide inputs for addressing operational and routing security requirements of Internet- connected networks, and, where appropriate, recommend work to be taken up by those working groups. Likewise, the working group will solicit inputs for its chartered work from those other working groups to strive for an optimal balance between objectives related to ease of operations and deployability, sustain scaling, enhance robustness, and optimize performance. Agenda time at GROW sessions at IETF meetings should allow for presentations and discussions of operator issues and experience, and other work within scope for the working group. The current GROW working group objectives are: * Present and discuss operational issues faced by the global routing system. * Document common terminology relevant to the maintenance and operation of the global routing system. * Document Best Current Practices for operations of the global routing system. * Document the operational aspects of securing the Internet routing system. * Provide guidance and recommendations for operating the global routing system. * Standardize YANG data models and automation building blocks related to the operations of global routing system. * Document BGP operational aspects of IP interconnection. * Provide documentation to assist in preventing malpractice in the global routing system. * Determine the effect of IGP extensions on the stability of the global routing system. * Provide maintenance for the BGP Monitoring Protocol (BMP), including fixes, extensions, and future versions. * Provide maintenance for the Multi-Threaded Routing Toolkit (MRT) Routing Information Export Format. Work related to SIDR operations (consisting of RPKI, Origin Validation of BGP announcements, and BGPSEC operations) will occur in SIDROPS working group. Milestones: Done - "Support for Local RIB in BGP Monitoring Protocol (BMP)" to IESG Done - "BMP Peer Up Message Namespace" to IESG Done - "Revision to Registration Procedures for Multiple BMP Registries" to IESG Jul 2025 - Submit a YANG Data Model for BGP Communities to the IESG Jul 2025 - Submit AS Path Prepending to the IESG Jul 2025 - Submit New BGP Monitoring Protocol (BMP) Statistics Types to the IESG Sep 2025 - Submit a Recommendation to avoid use of BGP Extended Communities at Internet Exchange Route Servers to the IESG Oct 2025 - Submit a YANG Data Model for BMP to the IESG Nov 2025 - TLV support for BMP Route Monitoring and Peer Down Messages to IESG Nov 2025 - Submit BMP Extensions to the IESG Dec 2025 - Submit TCP-AO Protection for BMP to the IESG Feb 2026 - Submit Near Real Time Mirroring (NRTM) version 4 to the IESG Apr 2026 - Submit Updated BGP Operations and Security to the IESG Apr 2026 - Submit Terminology in Global Routing Operations to the IESG Dec 2026 - Submit Peering API to the IESG