[Idr] Re: WG last call and IPR call for draft-ietf-idr-rt-derived-community (December 11, 2025 to January 5, 2026)

[[e-mail]]

HI Jie,

 

Few comments:

 

Section 3:

*	Two typos: s/Subt-Types/Sub-Types/g

 


Section 4:

*	The fact that we consider the type being the first byte for most of
the ext comms expect for IPv6 ones where we consider the two first bytes is
really confusing (subtype is within type). I know that it's following how
it's defined at IANA, but this is really creating confusion while RFC5701
still needs "subtype" field properly. Maybe at least for the example given
about Type 0x0011, we could mention that we talk about sub-type 0x11 used
for RT vs the general 0x02. Otherwise, we try to compare things that are not
directly comparable.

 

*	"When a new type is defined and registered, the corresponding.",
it's not clear what we are talking about, I guess we talk about new types of
RT derived EC. The entire paragraph does not sound super clear to me. Can we
simplify ? Previous paragraph says that we cannot guarantee subtype 0x02 for
any new RT created, then we can say that similarly we cannot guarantee that
new RT derived ECs, will get sub-type 0x15. BTW, wouldn't it be something we
would like to enforce to simplify operation/understanding ? (so sub-type
0x02 is always RT, 0x15 always for RT-derived EC)

 

 

Section 6 (Security):

I agree that this document is not defining how these ECs are used, however,
as they could potentially influence some indirect behaviors (not defined in
this document), it should be good to mention that user should pay attention
to stripping unintended received ECs from external peers.

 

 

 

From: Dongjie (Jimmy) <jie.dong=[e-mail]> 
Sent: Thursday, December 11, 2025 2:35 AM
To: idr <[e-mail]>
Cc: idr-chairs <[e-mail]>
Subject: [Idr] WG last call and IPR call for
draft-ietf-idr-rt-derived-community (December 11, 2025 to January 5, 2026)

 

This begins the working group last call for the draft on "Extended
Communities Derived from Route Targets":
https://datatracker.ietf.org/doc/draft-ietf-idr-rt-derived-community/

 

Due to the holiday season in the end of the year, this last call ends on
January 5th, 2026 so as to give the working group time to review and
comment. 

 

For purposes of the shepherd's report and according to IETF BCP 78/79, the
authors are requested to declare whether they are aware of any undisclosed
IPR covering this draft. Members of the working group are similarly
obligated to report any IPR they are aware of as well.

 

Best regards,

Jie (as WG secretary & document shepherd)