From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: [Make-wifi-fast] Reform of the ietf recall process
Date: Fri, 5 Apr 2019 18:19:19 +0200 [thread overview]
Message-ID: <CAA93jw5qXtZv4E9uQvxDKU_79U8_6oanGkJP1e+MXeEtxEQmeA@mail.gmail.com> (raw)
In-Reply-To: <6.2.5.6.2.20190405085139.0d5c39b0@elandnews.com>
is here: https://tools.ietf.org/html/draft-moonesamy-recall-rev-01
To me, this still doesn't go far enough. I think that everyone that
has ever got an RFC published deserves a vote.
The first four paragraphs of Section 7.1 of [RFC7437] are replaced by
the following:
At any time, at least 10 members of the IETF community, may request
by signed petition (email is acceptable) to the Internet Society
President the recall of any sitting IAB or IESG member, IETF Trustee
or IETF LLC Director. All signatories must have registered to attend
and have participated physically or remotely at least three out of
the previous five IETF meetings.
Each signature must include a full name, email address, and primary
company or organization affiliation. No more than two signatories
may have the same primary affiliation.
The IETF Secretariat is responsible for confirming that each
signatory is qualified. A valid petition must be signed by qualified
signatories as specified in this section.
---------- Forwarded message ---------
From: S Moonesamy <sm+ietf@elandsys.com>
Date: Fri, Apr 5, 2019 at 6:10 PM
Subject: AD Sponsorship of draft-moonesamy-recall-rev
To: <chair@ietf.org>, <iesg@ietf.org>
Cc: John C Klensin <john-ietf@jck.com>, <ietf@ietf.org>
Dear General Area Director,
In March, I sent a message to the IETF discussion list about the
recall process. As you are probably aware, there was a lively
discussion on the subject. I submitted an I-D [1] about the
subject. There were a comments on the I-D and they were addressed in
draft-moonesamy-recall-rev-01
I am enquiring about whether you, or any other Area Director, would
like to sponsor the I-D or whether you would like a proposal for a
working group to look into the draft and other related issues.
Regards,
S. Moonesamy
1. https://tools.ietf.org/html/draft-moonesamy-recall-rev-01
--
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740
next parent reply other threads:[~2019-04-05 16:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6.2.5.6.2.20190405085139.0d5c39b0@elandnews.com>
2019-04-05 16:19 ` Dave Taht [this message]
2019-04-05 21:33 ` [Make-wifi-fast] [Cerowrt-devel] " Valdis Klētnieks
2019-04-05 21:41 ` Dave Taht
2019-04-06 6:57 ` [Make-wifi-fast] [Bloat] " Mikael Abrahamsson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw5qXtZv4E9uQvxDKU_79U8_6oanGkJP1e+MXeEtxEQmeA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=make-wifi-fast@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox