Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>,
	cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
	Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Reform of the ietf recall process
Date: Fri, 05 Apr 2019 17:33:01 -0400	[thread overview]
Message-ID: <7219.1554499981@turing-police> (raw)
In-Reply-To: <CAA93jw5qXtZv4E9uQvxDKU_79U8_6oanGkJP1e+MXeEtxEQmeA@mail.gmail.com>

On Fri, 05 Apr 2019 18:19:19 +0200, Dave Taht said:

>    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.

Well... that rules me out, I've never actually made it to an IETF or NANOG. But
that "must have attended a physical meeting" has been there for ages now.

>    Each signature must include a full name, email address, and primary
>    company or organization affiliation.

Wait, what?  I need an affiliation?  At the moment I'm officially retired, does
that mean that even if I made it to meetings I have no say?

  reply	other threads:[~2019-04-05 21:33 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
2019-04-05 21:33   ` Valdis Klētnieks [this message]
2019-04-05 21:41     ` Dave Taht
2019-04-06  6:57     ` [Cerowrt-devel] [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/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7219.1554499981@turing-police \
    --to=valdis.kletnieks@vt.edu \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --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