Skip to main content

Effective Terminology in IETF Documents
charter-ietf-term-00-07

Yes

Erik Kline
Roman Danyliw
(Lars Eggert)
(Martin Vigoureux)

No Objection

Francesca Palombini

Note: This ballot was opened for revision 00-00 and is now closed.

Ballot question: "Is this charter ready for external review?"

Erik Kline
Yes
Roman Danyliw
Yes
Zaheduzzaman Sarker
Yes
Comment (2021-03-24 for -00-02) Sent
This is very timely and necessary  work, thanks for chartering it.

I think the charter should clarify if the working group outcome will impact only the future technical documentations or this might lead to changes in existing technical documents where non-inclusive terminologies are used (as per the recommendation by the working group)
Francesca Palombini
No Objection
Murray Kucherawy
No Objection
Comment (2021-03-24 for -00-02) Not sent
I concur with Alvaro's comments.
Éric Vyncke
No Objection
Comment (2021-03-25 for -00-02) Sent
While I am very skeptical whether any informational RFC will change anything or have any useful impact, let's go with the flow...

I have two comments though:

"The RFC will express general principles for *judging* when language is inclusive or exclusive. ", can we replace 'judging' by something else ? Suggest 'evaluating'

"The principles should match the expectations from *a broad set* of IETF participants.", what is the semantic of "broad" here? Does this mean 50% of the participants? 50% of the vocal participants ? Coming from a country, Belgium, where even 5% of population can rightfully block some legislations, I would prefer some text about 'diversity' (that itself is also fuzzy). For example, it seems that some Italian people do not appreciate the wording "spaghetti code" (and I can understand them) even if IETF participants from Italy is probable less than 5%.

-éric
Lars Eggert Former IESG member
Yes
Yes (for -00-02) Sent

                            
Martin Duke Former IESG member
Yes
Yes (2021-03-15 for -00-00) Sent
Thank you for chartering this work.

The charter is unclear if terminology that is not related to inclusivity is in-scope or not. For example, the QUIC documents use a concept of off-path attacker that is a little different from the meaning that I thought was commonly held.

I have no strong feeling on whether or not it should be in scope, but the charter should be clear about this.
Martin Vigoureux Former IESG member
Yes
Yes (for -00-02) Not sent

                            
Robert Wilton Former IESG member
Yes
Yes (2021-03-25 for -00-02) Not sent
I'm glad to see this work finally happening!
Alvaro Retana Former IESG member
No Objection
No Objection (2021-03-23 for -00-02) Sent
I don't think that using rfc7322 as justification/background for this work is needed or appropriate.  rfc7322, while very useful, is not an IETF consensus document.

Also, the output of this work should not be to recommend any action to be taken by the RPC; the authors should act on the recommendations.  Taking the rfc7322 reference out may also remove any potential assumption that the RPC should be involved.
Benjamin Kaduk Former IESG member
No Objection
No Objection (2021-03-25 for -00-02) Sent
I'd suggest s/judging/assessing/ in the vein of what was noted already.

It's not clear that work in this space is properly a "one and done"
exercise vs a continuing endeavor to adapt as situations change.  That
said, having a single immediate concrete goals does seem wise as a
start.