[Idr] Re: I-D Action: draft-ietf-idr-rfc4360-bis-00.txt

[Robert Raszuk <[e-mail]>]

Hi Nat,

Isn't this a bit circular dependency to still list in -bis original
(obsoleted) RFC4360 as Normative Reference ? :)

   [RFC4360]  Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended
              Communities Attribute", RFC 4360, DOI 10.17487/RFC4360,
              February 2006, <https://www.rfc-editor.org/info/rfc4360>.

Recommend you remove it.

- - -

Aside shouldn't we also -bis two other RFCs namely: RFC5668 and RFC5701 and
paste the below text
to them along with a few other cosmetic changes ?

   If a route has non-transitive extended communities, those communities
   SHOULD NOT be propagated across an Autonomous System boundary and
   SHOULD be removed from the route.  However, non-transitive extended
   communities SHOULD NOT be removed when advertising the route within
   the same BGP AS Confederation(as defined in [RFC5065]).  As part of
   configuration or BGP protocol extensions, BGP speakers MAY attach
   non-transitive extended communities to routes advertised across
   Autonomous System boundaries.

   By default, when a BGP speaker receives routes with non-transitive
   extended communities across Autonomous System or Confederation
   Member-AS boundaries, it SHOULD NOT remove these extended
   communities.  The behavior MAY be configurable.  The BGP speaker
   SHOULD also allow local policies to match against or remove these
   extended communities.


Those two do list RFC4360 as Normative Reference so perhaps when RFC4360 is
obsolete and replaced by RFC4360-bis we do not need to touch those RFCs
....

Regards,
Robert


On Sat, Sep 6, 2025 at 5:11 PM Nat Kao <[e-mail]> wrote:

> Hello, WG.
>
> This version updates the RX behaviors of non-transitive ECs based on the
> feedback from the WG.
>
> Please kindly review. ;)
>
> The diff from the original RFC4360 is at:
>
> https://author-tools.ietf.org/iddiff?url1=4360&url2=draft-ietf-idr-rfc4360-bis-00&difftype=--html
>
> The current proposal of the "IANA Considerations" section is at this
> GitHub branch:
>
> https://github.com/ietf-wg-idr/draft-ietf-idr-rfc4360-bis/tree/chairs-01-iana-consideration-edit
>
> The HTML diff of the proposal is also attached.
>
> Suggestions are highly appreciated.
>
> Many Thanks,
> Nat
>
> On Sat, Sep 6, 2025 at 10:21 PM <[e-mail]> wrote:
>
>> Internet-Draft draft-ietf-idr-rfc4360-bis-00.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-00.txt
>>    Pages:   13
>>    Dates:   2025-09-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-00
>>
>> Internet-Drafts are also available by rsync at:
>> rsync.ietf.org::internet-drafts
>>
>>
>> _______________________________________________
>> Idr mailing list -- [e-mail]
>> To unsubscribe send an email to [e-mail]
>>
> _______________________________________________
> Idr mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
>