A new PR will addreess these issues, when rev'ed as an ID.
-- Obsolete informational reference (is this intentional?): RFC 2988 (Obsoleted by RFC 6298)
mea culpa for not spotting - we ought to replace by the later RFC.
-- Obsolete informational reference (is this intentional?): RFC 8312 (Obsoleted by RFC 9438)
That was intentional. The text of the PR has been updated to say this.
We can add a note that tunnels, and similar encaps need to consider nested congestion control interactions:
The design of tunnels and similar encapsulations might need to consider nested congestion control interactions. For example, when ECN is used by an IP and lower layer technology {{ECN-encaps}}.
Added 2119. I don't know where the BCP number ought to be placed in markdown, I can do it xml;-0. If we can't figure it out, we could let RFC-Ed do it at the end, the context is there.
A new PR will addreess these issues, when rev'ed as an ID.
mea culpa for not spotting - we ought to replace by the later RFC.
That was intentional. The text of the PR has been updated to say this.
The design of tunnels and similar encapsulations might need to consider nested congestion control interactions. For example, when ECN is used by an IP and lower layer technology {{ECN-encaps}}.