Re: Babel maintenance included in future work?

> Therefore, I think we need a plan/agreed_draft for re-charter, and please help
> me/WG with a clear plan/milestones that we can work/discuss forward and we can
> make more drafts/discussions/decisions.

The plan is to do absolutely nothing.  That's what the word "maintenance"
is meant to imply.

Here's the Babel charter:

  https://datatracker.ietf.org/wg/babel/about/

Here's the list of RFCs that we produced:

  https://datatracker.ietf.org/wg/babel/documents/

Unless I'm mistaken, we've done all of the work that we promised to do,
and more.  Hence, our plan is to do absolutely nothing, unless there is
a good reason to do something.

Of course, we'll be doing something while we do nothing:

  - improve the implementations (BIRD and babeld);
  - add a competent testing framework (I've got an engineer working on that);
  - help people deploy Babel in production networks;
  - travel around the world and give talks about Babel.

While none of this obviously involves the IETF, it might conceivably lead
to us wanting to publish an RFC.  For example, we might want to publish an
Informational RFC with implementation advice, or with deployment advice,
or we might end up implementing draft-chouasne-babel-tos-specific and
revive the draft.

Hence, we need a home at IETF, and that home is MANET.  With its friendly
chairs and competent participants, MANET is just the right place to be
doing nothing.

-- Juliusz