Skip to content

More strongly recommend ECN marking #3373

@martinthomson

Description

@martinthomson

In #3320, @mirjak suggested that a different algorithm might be better to recommend enabling ECN and only disabling it if a failure is detected.

That algorithm adopts the same posture as the draft: that ECN is optional and that endpoints are permitted to be cautious in enabling it. If we want to adopt the view that ECN works and endpoints are required to use it unless it breaks, that's a bigger change.

I open this issue, while being aware that this is re-opening something we discussed and agreed previously, without there being new information to present. Chairs, if you do think we should discuss this, it's a design issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    -transportdesignAn issue that affects the design of the protocol; resolution requires consensus.has-consensusAn issue that the Chairs have determined has consensus, by canvassing the mailing list.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions