| Internet-Draft | Suspending Posting Rights | August 2024 |
| Moonesamy | Expires 18 February 2025 | [Page] |
The practice for revoking and restoring posting rights is specified in RFC 3683. The discussions for revoking posting rights stirred controversy. This document specifies a procedure for suspending posting rights to all written channels of communication used for the IETF Standards Process.¶
This document obsoletes RFC 3683.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 18 February 2025.¶
Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
[RFC3683] defines a practice for revoking and restoring posting rights to IETF mailing lists. The practice to revoke posting rights was invoked six times since 2006. Section 2 discusses some of the issues affecting the application of the practice. Section 3 specifies the procedure for suspending posting rights to all written channels of communication used for the IETF Standards Process [RFC2026].¶
The practice specified in [RFC3683] requires an Area Director to invoke the it and the IESG to initiate a "PR-action" as a Last-Call. There may be a perception that the outcome of the Last-Call is a foregone conclusion.¶
The practice was invoked twice over the past two years. Some of the comments on the Last-Calls were viewed as controversial.¶
Posting rights can be restored a year after the posting rights action was revoked. The procedure to do that was never invoked. As a consequence, the revocation of posting rights could be construed as permanent.¶
The procedure for suspending posting rights to all written channels of communication used for the IETF Standards Process is invoked by signed petition. The petition requires at least 10 signatories with no more than two of the signatories having the same primary affiliation. The maximum suspension period is two years. The petition is evaluated by the IESG. The IESG shall publish a rationale for its decision within a period of four weeks.¶
This document discusses IETF procedures. It raises no security issues for the Internet.¶
This document does not require any IANA actions.¶