<?xml version="1.0" encoding="utf-8"?>
<?xml-model href="rfc7991bis.rnc"?>
<!-- Required for schema validation and schema-aware editing -->
<!-- <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?> -->
<!-- This third-party XSLT can be enabled for direct transformations in XML processors, including most browsers -->
<!DOCTYPE rfc [
<!ENTITY nbsp "&#160;">
<!ENTITY zwsp "&#8203;">
<!ENTITY nbhy "&#8209;">
<!ENTITY wj "&#8288;">
]>

<rfc
  xmlns:xi="http://www.w3.org/2001/XInclude"
  category="bcp"
  docName="draft-moonesamy-bcp83-bis-00"
  ipr="trust200902"
  obsoletes="3683"
  submissionType="IETF"
  xml:lang="en"
  version="3">
  <front>
    <title abbrev="Suspending Posting Rights">
      Suspending Posting Rights</title>
	<author initials='S.' surname='Moonesamy' fullname='Subramanian Moonesamy'>
       <organization/>
	<address> 	  
          <email>sm+ietf@elandsys.com</email>
      </address>
   </author>
    <date month="August" day="17" year="2024"/>
    <abstract>
      <t>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.</t>
     <t>This document obsoletes RFC 3683.</t>
    </abstract>
  </front>

  <middle>

<section title="Introduction">
    <t><xref target="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.
    <xref target="issues"/> discusses some of the issues affecting the
	application of the practice.
	<xref target="suspend"/> specifies the procedure for suspending posting
	rights to all written channels of communication used for the IETF
	Standards Process <xref target="RFC2026"/>.</t>
 </section>
 <section title="Issues" anchor="issues">
    <t>The practice specified in
      <xref target="RFC3683"/>
	  requires an Area Director to invoke the it and the IESG
	  to initiate a &quot;PR-action&quot; as a Last-Call. There may be a perception that the outcome
	  of the Last-Call is a foregone conclusion.</t>
	 <t>The practice was invoked twice over the past two years.  Some
         of the comments on the Last-Calls were viewed as controversial.</t>
    <t>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.</t>
 </section>
 <section title="Suspending Posting Rights" anchor="suspend">
    <t>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.</t>
</section>
  <section title="Security Considerations">
    <t>This document discusses IETF procedures.  It raises no security
	  issues for the Internet.</t>
    </section>
    <section title="IANA Considerations">
        <t>This document does not require any IANA actions.</t>
	</section>
  </middle>
 
  <back>

    <references  title="Normative References">
      <xi:include
    href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2026.xml"/>
      <xi:include
    href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3683.xml"/>
    </references>

  </back>
</rfc>
