anyone with a worthy i-d which is not gonna make it as an RFC could do
worse than consider submiting it to INET....a lot of the papers there
are in that line and would then count as prior art, be archival, and
citable.
possible source of pressure/problem:
interestingly enough, in tenure, most universities in the US
to my knowledge (on
checking recently) don't admit of RFCs at all as part of the
publiations list in a CV...this may be good in some senses, as it
stops researchers trying to use the IETF as a place to get visibility
for tenures sake alone (but shouldnt put them off if they have
geneuine working code and think they;ll get consensus roughly:-)
escape valve::
so if i have a recommendation for folsk with well worked out i-ds,
its "find a good workshop - e.g. ieee sponsored, but also isoc or acm
or other and send it there" - alternatives too are some of the
magazines and newsletters e.g. IEEE Network (publishes the most cited
work on RSVP for example) and ACM CCR (publishes a lot of inciteful
work on protocol implementation and experience...)
j.