Protocol Action: 'BGP Extended Communities Attribute' to Proposed Standard (draft-ietf-idr-rfc4360-bis-09.txt)

The IESG <iesg-secretary@ietf.org> Tue, 14 July 2026 15:21 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.21.112] (gaia.k8s.ietf.org [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id CF8321169F7D6; Tue, 14 Jul 2026 08:21:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1784042480; bh=kF8dquja9WEGSMAv35AJHbhDKG0Somn1DsrG8Bo5SqY=; h=From:To:Subject:Cc:Date; b=jYpW7Zdh3Id3fIFrA9FyUWSiIMaMkXg8Y+4ShzxeShUXgTrzUUv2nGhR1XBRWmglO Ij1PTbDUNjQ8eVAYojXePOF46tDJD1VfR4ozU+2plXlvQl7D8ChoPQ9idClHhmbWd7 AHXttrbPs+1KFtKuc68rZKw7hqMqMkBJUljbB1SI=
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: Protocol Action: 'BGP Extended Communities Attribute' to Proposed Standard (draft-ietf-idr-rfc4360-bis-09.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 12.69.0
Auto-Submitted: auto-generated
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <178404248077.549099.15669294270922512973@dt-datatracker-d4d6ff9d9-kg6bf>
Date: Tue, 14 Jul 2026 08:21:20 -0700
Message-ID-Hash: 6VAZDTEIHTOFD5HMDXW6P4TK6FM3SZXA
X-Message-ID-Hash: 6VAZDTEIHTOFD5HMDXW6P4TK6FM3SZXA
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>, draft-ietf-idr-rfc4360-bis@ietf.org, idr-chairs@ietf.org, idr@ietf.org, keyur@arrcus.com, rfc-editor@rfc-editor.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/FRsK1VdX2BmnBJ1LXXlAWp-Uh-M>
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 IESG has approved the following document:
- 'BGP Extended Communities Attribute'
  (draft-ietf-idr-rfc4360-bis-09.txt) as Proposed Standard

This document is the product of the Inter-Domain Routing Working Group.

The IESG contact persons are Gunter Van de Velde, Jim Guichard and Ketan
Talaulikar.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-idr-rfc4360-bis/




Technical Summary

   This document describes the "extended community" BGP-4 attribute.
   This attribute provides a mechanism for labeling information carried
   in BGP-4.  These labels can be used to control the distribution of
   this information, or for other applications.

   This document obsoletes RFC 4360.  This document also updates RFC
   5701 by incorporating the operations section.

Working Group Summary

   There was good discussion and participation between a diverse
   set of WG participants on producing this document to revise
   the base RFC4360 to clarify on an important aspect related
   to handling of transitivity property. There was some
   discussion on changing the type/sub-type convention and how
   extended communities are organized, but the WG converged on
   not changing things which were widely implemented and deployed.

Document Quality

   There are multiple implementations of the changes introduced
   by this document to the base RFC4360. The base RFC4360 itself
   has widespread support and deployment. Many other implementations
   are in the process of supporting the new changes.

   The document has undergone a good set of reviews within the WG
   as well as from BGPDIR and RTGDIR.

Personnel

   The Document Shepherd for this document is Keyur Patel. The Responsible
   Area Director is Ketan Talaulikar.