|
Roni Even said: “I do not think that the IETF should accept any
work because people want to do it, if this is the case a group of people can
come and ask to start working on any idea they have that has some relation to
the Internet. IETF should accept work that is in scope for of the IETF
and for which there is enough knowledge to evaluate the work by the
participants.” I would like to suggest two principles that appear to have
guided decisions of this kind in the past: 1.
The “scope” of the Internet Engineering
Task Force (IETF) is work relating to Internet Engineering. 2.
Standards work is best carried out within the
organization that potential active participants prefer to work in. These principles suggest that if proposed work relates to
Internet Engineering and a group of people are both interested in doing work in
the IETF and have demonstrated competence, then that work can be chartered
within the IETF. Witness the chartering of the TRILL and CAPWAP WGs. In
these cases, participants expressed a preference to do the work within the IETF,
and demonstrated the competence to take it on. Those WGs were chartered
within IETF. Similar decisions were made with respect to WGs that
subsequently landed in the Sub-IP Area. There have also been situations where work was clearly related
to Internet Engineering, but it was also clear that participants preferred to
do that work elsewhere. In that case, the IETF transferred the work to
another SDO (see RFC 4663). |
_______________________________________________ Ietf mailing list Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf