![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
> -----Original Message----- > From: smb at cs.columbia.edu [mailto:smb at cs.columbia.edu] > > In message <200509271059.GAA29066 at ietf.org>, "Nick Staff" writes: > > > >> ] > >> ] 7.2 Approval to block participant on a WG list (Bert > >> Wijnen) ] ] This management issue was discussed. The IESG agrees > >> that Bert ] Wijnen may block posting rights for Dean > Anderson on the > >> dnsops ] mailing list if he refuses to stay on topic as > per the list > >> rules. > >> > >> which raises the question, "Why are we even discussing this?" > >> > >> -- > >> John Leslie <john at jlc.net> > >> > >John- > > > >Could you please specify the RFC that details the procedure > for when an > >AD requests that the IESG remove someone's posting > privileges from the > >IETF list (the RFC other 3683 of course). If there isn't > one then I'd > >have to ask that you refrain from making wildly unsupported > claims as > >they are disruptive to the process. > > > > Have a look at 3934. > > --Steven M. Bellovin, http://www.cs.columbia.edu/~smb > Steve, I might have misunderstood it, but I thought 3934 only pertained to suspension from a Working Group list and that since David's request included suspension from the main IETF list that it fell under 3683? nick _______________________________________________ Ietf mailing list Ietf at ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.