ietf-wg-ccwg / rfc5033bis

IETF drafts
Other
4 stars 6 forks source link

Minor update to fix NiTs from Shepherd Review #122

Closed gorryfair closed 4 months ago

gorryfair commented 4 months ago

A new PR will addreess these issues, when rev'ed as an ID.

  1. -- 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.

  1. -- 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.

  1. 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}}.

gorryfair commented 4 months ago

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.