[secdir] [new-work] WG Review: Global Routing Operations (grow)

The IESG <iesg@ietf.org> Thu, 24 April 2025 15:44 UTC

Return-Path: <forwardingalgorithm@ietf.org>
X-Original-To: secdir@mail2.ietf.org
Delivered-To: secdir@mail2.ietf.org
Received: from mail2.ietf.org (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 66AA920BCFB4 for <secdir@mail2.ietf.org>; Thu, 24 Apr 2025 08:44:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1745509449; bh=/vEij/w79aRHCJp5qyNsKcQZ1iApBij2XBxS5bMCazY=; h=From:To:Date:Reply-To:Subject:List-Id:List-Archive:List-Help: List-Owner:List-Post:List-Subscribe:List-Unsubscribe; b=oybXa3hqBBi1CGyMQhwpRup09aP/TH2QUtsQBcFCkC3Eh+IrVpTmR0E4CMkRxp6Ee yvVSvy7yhn1oNmQf41uA5ghgd6w7xwWPZbmQjqckgL5o40iF0GTERCrIUUzuDUmvyw 4iDHOYdidx3zmqO3bFx+jvzBj5riFLXn+qMAO+8Y=
X-Mailbox-Line: From new-work-bounces+secdir=ietf.org@ietf.org Thu Apr 24 08:44:09 2025
Received: from mail2.ietf.org (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 4958D20BCFB0 for <secdir@ietf.org>; Thu, 24 Apr 2025 08:44:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1745509449; bh=/vEij/w79aRHCJp5qyNsKcQZ1iApBij2XBxS5bMCazY=; h=From:To:Date:Reply-To:Subject:List-Id:List-Archive:List-Help: List-Owner:List-Post:List-Subscribe:List-Unsubscribe; b=oybXa3hqBBi1CGyMQhwpRup09aP/TH2QUtsQBcFCkC3Eh+IrVpTmR0E4CMkRxp6Ee yvVSvy7yhn1oNmQf41uA5ghgd6w7xwWPZbmQjqckgL5o40iF0GTERCrIUUzuDUmvyw 4iDHOYdidx3zmqO3bFx+jvzBj5riFLXn+qMAO+8Y=
X-Original-To: new-work@ietf.org
Delivered-To: new-work@mail2.ietf.org
Received: from [10.244.8.129] (unknown [104.131.183.230]) by mail2.ietf.org (Postfix) with ESMTP id 28E5420BC6E8 for <new-work@ietf.org>; Thu, 24 Apr 2025 08:43:17 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
From: The IESG <iesg@ietf.org>
To: new-work@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.38.0
Auto-Submitted: auto-generated
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Reply_to: <iesg@ietf.org>
Message-ID: <174550939704.2584560.9458846426435769181@dt-datatracker-64c5c9b5f9-hz6qg>
Date: Thu, 24 Apr 2025 08:43:17 -0700
X-MailFrom: iesg@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-new-work.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Content-Transfer-Encoding: base64
Message-ID-Hash: QICIDKIXDYXZODQP2QITKCEDGONP5IDN
X-Message-ID-Hash: QICIDKIXDYXZODQP2QITKCEDGONP5IDN
X-MailFrom: forwardingalgorithm@ietf.org
X-Mailman-Rule-Hits: nonmember-moderation
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-secdir.ietf.org-0
Reply-To: iesg@ietf.org
Subject: [secdir] [new-work] WG Review: Global Routing Operations (grow)
List-Id: Security Area Directorate <secdir.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/H1AhgiWkKB3hT_QNcfzhqwRICsc>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Owner: <mailto:secdir-owner@ietf.org>
List-Post: <mailto:secdir@ietf.org>
List-Subscribe: <mailto:secdir-join@ietf.org>
List-Unsubscribe: <mailto:secdir-leave@ietf.org>

The Global Routing Operations (grow) WG in the Operations and Management Area
of the IETF is undergoing rechartering. The IESG has not made any
determination yet. The following draft charter was submitted, and is provided
for informational purposes only. Please send your comments to the IESG
mailing list (iesg@ietf.org) by 2025-05-04.

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



_______________________________________________
new-work mailing list -- new-work@ietf.org
To unsubscribe send an email to new-work-leave@ietf.org