search

ietf-tapswg / api-drafts

Architecture, interface, and implementation drafts for the definition of an abstract API for IETF TAPS
Other
23 stars 15 forks source link

Ignore => None #1422

Closed mwelzl closed 1 year ago

mwelzl commented 1 year ago

Closes #1310

I like it a little better with this change, but I remember that we had a real discussion about "Ignore", this term wasn't "just" picked - I believe @abrunstrom was a part of this discussion.

There are good reasons for either choice, I think. If you want a good reason for keeping "Ignore", look at one of the tables at the end of this PR: "congestionControl: none" and "preserveMsgBoundaries: none" can easily be taken to mean "no congestion control" and "no boundaries". Of course this could be solved by calling it "no preference" (but then it's two words, not one, and also "preference" is the name of the type itself).

I have no strong opinion here. Let's have a quick chat about this and decide.

mwelzl commented 1 year ago

Agreement: change it to noPreference