[Mod-discuss] Re: WG Last Call: draft-ietf-modpod-group-processes-10 (Ends 2025-09-08)

[Brian E Carpenter <[e-mail]>]

Hi,

I think this draft is in very good shape, but after a careful read I have a few comments and suggestions listed below. I also hope that it will be reviewed by counsel, because moderation of an open standards discussion is a somewhat sensitive topic.

> Abstract
> 
> The IETF community will treat people with kindness and grace, but not endless patience.

I strongly agree with that sentence but I think it belongs in the Introduction, not in the Abstract.

>  1.1. Background 
...
>  And the IETF list for general discussions has, mostly for historic reasons, a team of moderators ...

I think "mostly for historic reasons" is a little bit disingenuous. I suggest deleting the phrase rather than debating it, because it adds no value.

>  2.1. Composition
> 
> The moderator team consists of no less than five individuals. 

I am concerned that "no less than" could be problematic if a team member departs unexpectedly. Adding a weasel word such as "normally" would be good.

>  4.1. Consistency and Conflict Resolution 
>...
> any moderation decision can be appealed to the IESG by anyone, per [RFC2026]

1) Cite Section 6.5 of RFC2026 to be more precise.
2) That section applies explicitly to disagreement "with a Working Group recommendation." We're stretching that a little bit, so in my opinion "per [RFC2026]" isn't enough. I suggest:

... any moderation decision can be appealed to the IESG by anyone, and treated as a standards process disagreement acccording to Section 6.5 of [RFC2026]

>  5. Relationship to other IETF functions 

Should we say anything about the other RFC streams (IAB, Independent, Editorial) or about the RFC Editor?

>  Appendix B. Problems with the Previous Approach 
>...
> PR-actions, which can address disruptive behavior across several lists, are cumbersome and slow, 

Cite RFC3683 here.

Regards/Ngā mihi
    Brian Carpenter

On 26-Aug-25 04:59, Lisa Dusseault via Datatracker wrote:
> 
> Subject: WG Last Call: draft-ietf-modpod-group-processes-10 (Ends 2025-09-08)
> 
> This message starts a 2-week WG Last Call for this document.
> 
> Abstract:
>     The IETF community will treat people with kindness and grace, but not
>     endless patience.
> 
>     This memo describes the moderation of disruptive participation across
>     the IETF's various public contribution channels and discussion fora.
>     It establishes guardrails for moderation and a moderator team.  That
>     team will develop a uniform set of guidelines and facilitate their
>     consistent implementation with chairs and administrators.
> 
> File can be retrieved from:
> https://datatracker.ietf.org/doc/draft-ietf-modpod-group-processes/
> 
> Please review and indicate your support or objection to proceed with the
> publication of this document by replying to this email keeping
> [e-mail] in copy. Objections should be motivated and suggestions
> to resolve them are highly appreciated.
> 
> Authors, and WG participants in general, are reminded again of the
> Intellectual Property Rights (IPR) disclosure obligations described in BCP 79
> [1]. Appropriate IPR disclosures required for full conformance with the
> provisions of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of
> any. Sanctions available for application to violators of IETF IPR Policy can
> be found at [3].
> 
> Thank you.
> 
> [1] https://datatracker.ietf.org/doc/bcp78/
> [2] https://datatracker.ietf.org/doc/bcp79/
> [3] https://datatracker.ietf.org/doc/rfc6701/
> 
> 
> 
> _______________________________________________
> Mod-discuss mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]