Hi all,
I had a clash during the yesterday BCOP TF meeting, so looked at the slides and video online today.
Regarding the "Documenting the RIPE Consensus Processā, I agree that we could do something and I will like to participate in the effort. Also I agree with the inputs from different people in the mic, but still think we can have some progress in a document that can be useful for the community.
Tks!
Regards,
Jordi
@jordipalet
**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
The IPv6 Company
This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.
Dear BCOP TF community,
We are looking forward to another BCOP TF session in Prague at RIPE89!
After the report from "Documenting the best operational practices of
running networks during the war (Ukraine)" topic - we'll open a
discussion about if we should start documenting what our community
consensus process actually is.
Currently, we use bits and pieces from the IETF and other organizations,
but the problem is that this is not documented anywhere and every RIPE
community member may have their own version in their mind.
That being said, I would like to invite all interested in this topic to
the BCOP TF session at the end of Monday, so we can discuss it, figure
out if we need this documented and (if yes) - maybe form a small group
of people that will start working on it.
https://ripe89.ripe.net/programme/meeting-plan/bcop-tf/
Cheers and thnx!
Benno and Jan, BCOP TF co-chairs
--
Anything that can be configured can be misconfigured. [RFC5505]
