Return-Path: 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 4C5A7967E116 for ; Sat, 6 Dec 2025 09:13:31 -0800 (PST) X-Virus-Scanned: amavisd-new at ietf.org X-Spam-Flag: NO X-Spam-Score: -2.1 X-Spam-Level: X-Spam-Status: No, score=-2.1 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, HTML_MESSAGE=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=pfrc.org 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 UufrAecgFudV for ; Sat, 6 Dec 2025 09:13:29 -0800 (PST) Received: from prospero.pfrc.org (prospero.pfrc.org [IPv6:2a02:4780:2d:e7d4::1]) (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 9656A967E10D for ; Sat, 6 Dec 2025 09:13:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pfrc.org; s=prospero20250622; t=1765041202; bh=oBq6CqyueSYxIn3GknKbVvp5cEES81dKUIKLvadSJQY=; h=Date:Subject:To:References:From:In-Reply-To:From; b=WLPBj9Y3BuI4+4IZ5W7u9qPDq9eTH+YGyH9ncdzkkamTqMNeHiPD9Df/K5TP55APn 5bJEAi38AbUnrWCAlU6g9KbLtIocxG48gcck4UZ5MDBwAiGE6VTq58oz5gb+OebcY6 c/0jKsNryRkKPldfw6SAX0BMKRoFIpaigPEdvUZaE2Cx3ipOUwyr1BD12unhdmS5Aq Li1bj7yUI+53VE68Ky/JCOubBOxsBXL7cHXp94YQ3A34nq/11guO10QeKPBn6php1+ W12elg5JbIAX5X8QhD45dbo1OPX2Vukf93MdKfN0uF2KvHisP009jWwBdiC14/rEGy NM+2imGCaadWg== Received: from [IPV6:2600:1702:80c0:8960:86d8:551:2180:bcd4] (unknown [IPv6:2600:1702:80c0:8960:86d8:551:2180:bcd4]) by prospero.pfrc.org (Postfix) with ESMTPSA id 9109A800E5 for ; Sat, 6 Dec 2025 17:13:22 +0000 (UTC) Content-Type: multipart/alternative; boundary="------------Bsoy3FpRA5LIgh4cIdPH7DBe" Message-ID: <5b3ebf3d-a784-4e19-902e-8b629925fd37@pfrc.org> Date: Sat, 6 Dec 2025 12:13:20 -0500 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: idr@ietf.org References: <176503792436.612123.15129580580559280962@dt-datatracker-5bd94c585b-wk4l4> Content-Language: en-US From: Jeffrey Haas In-Reply-To: Message-ID-Hash: 5DGVL57WAPTMBKXAG74SYHIAVGJQNSOC X-Message-ID-Hash: 5DGVL57WAPTMBKXAG74SYHIAVGJQNSOC X-MailFrom: jhaas@pfrc.org 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 X-Mailman-Version: 3.3.9rc6 Precedence: list Subject: =?utf-8?q?=5BIdr=5D_Re=3A_I-D_Action=3A_draft-ietf-idr-rfc4360-bis-02=2Etxt?= List-Id: Inter-Domain Routing Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: This is a multi-part message in MIME format. --------------Bsoy3FpRA5LIgh4cIdPH7DBe Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Thank you, Nat, for your continued hard work on this draft. This document should largely be ready for last call.  I have initiated a request for security and routing directorate review for the current version of the draft. The point below covering early registries is important for the WG to consider.  It is regularly the case that new extended type extended communities require sub-registries.  These sub-registries, especially for popular work in-progress, often end up maintaining the early registry in the defining draft. Permitting IANA to manage these new early registries will ease work for authors and the working groups.  However, in the current form, this creates a normative reference which will delay RFC publication.  A question to our AD is whether we can make this an informative reference? Please review this draft and supply feedback.  The IDR chairs will discuss when to initiate last call based on this feedback. -- Jeff On 12/6/25 11:27, Nat Kao wrote: > Hi, All. > > We've updated the following in this version(-02): > - IANA considerations > - Security considerations > - Notes about the 4-octet AS-specific ECs > - Misc text updates > > We've also briefly mentioned the early registry creation procedures in > sections 8.1.1 & 8.1.2 with references to > draft-baber-ianabis-early-registries. > We would like to know your opinions on this. > > The difference from the original RFC4360 is at: > https://author-tools.ietf.org/iddiff?url1=4360&url2=draft-ietf-idr-rfc4360-bis-02&difftype=--html > > > Please kindly review. > If you have any other suggestions, please let us know. > > Many Thanks! > Nat > > On Sun, Dec 7, 2025 at 12:19 AM wrote: > > Internet-Draft draft-ietf-idr-rfc4360-bis-02.txt is now available. > It is a > work item of the Inter-Domain Routing (IDR) WG of the IETF. > >    Title:   BGP Extended Communities Attribute >    Authors: Srihari Sangli >             Nat Kao >    Name:    draft-ietf-idr-rfc4360-bis-02.txt >    Pages:   22 >    Dates:   2025-12-06 > > Abstract: > >    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 [RFC4360]. > > The IETF datatracker status page for this Internet-Draft is: > https://datatracker.ietf.org/doc/draft-ietf-idr-rfc4360-bis/ > > There is also an HTMLized version available at: > https://datatracker.ietf.org/doc/html/draft-ietf-idr-rfc4360-bis-02 > > A diff from the previous version is available at: > https://author-tools.ietf.org/iddiff?url2=draft-ietf-idr-rfc4360-bis-02 > > Internet-Drafts are also available by rsync at: > rsync.ietf.org::internet-drafts > > > _______________________________________________ > Idr mailing list -- idr@ietf.org > To unsubscribe send an email to idr-leave@ietf.org > > > _______________________________________________ > Idr mailing list --idr@ietf.org > To unsubscribe send an email toidr-leave@ietf.org --------------Bsoy3FpRA5LIgh4cIdPH7DBe Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

Thank you, Nat, for your continued hard work on this draft.

This document should largely be ready for last call.  I have initiated a request for security and routing directorate review for the current version of the draft.

The point below covering early registries is important for the WG to consider.  It is regularly the case that new extended type extended communities require sub-registries.  These sub-registries, especially for popular work in-progress, often end up maintaining the early registry in the defining draft.  Permitting IANA to manage these new early registries will ease work for authors and the working groups.  However, in the current form, this creates a normative reference which will delay RFC publication.  A question to our AD is whether we can make this an informative reference?

Please review this draft and supply feedback.  The IDR chairs will discuss when to initiate last call based on this feedback.

-- Jeff


On 12/6/25 11:27, Nat Kao wrote:
Hi, All.

We've updated the following in this version(-02):
- IANA considerations
- Security considerations
- Notes about the 4-octet AS-specific ECs
- Misc text updates

We've also briefly mentioned the early registry creation procedures in sections 8.1.1 & 8.1.2 with references to draft-baber-ianabis-early-registries.
We would like to know your opinions on this.

The difference from the original RFC4360 is at:
https://author-tools.ietf.org/iddiff?url1=4360&url2=draft-ietf-idr-rfc4360-bis-02&difftype=--html

Please kindly review.
If you have any other suggestions, please let us know.

Many Thanks!
Nat

On Sun, Dec 7, 2025 at 12:19 AM <internet-drafts@ietf.org> wrote:
Internet-Draft draft-ietf-idr-rfc4360-bis-02.txt is now available. It is a
work item of the Inter-Domain Routing (IDR) WG of the IETF.

   Title:   BGP Extended Communities Attribute
   Authors: Srihari Sangli
            Nat Kao
   Name:    draft-ietf-idr-rfc4360-bis-02.txt
   Pages:   22
   Dates:   2025-12-06

Abstract:

   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 [RFC4360].

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-idr-rfc4360-bis/

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-idr-rfc4360-bis-02

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-idr-rfc4360-bis-02

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts


_______________________________________________
Idr mailing list -- idr@ietf.org
To unsubscribe send an email to idr-leave@ietf.org

_______________________________________________
Idr mailing list -- idr@ietf.org
To unsubscribe send an email to idr-leave@ietf.org
--------------Bsoy3FpRA5LIgh4cIdPH7DBe--