> For the documents that are to become RFCs, I most heartily agree.
> Keeping the community informed of what we are doing in detail is slightly
> different - this is not developing a document, it's keeping our notebook in
> a public place.
I agree with Harald that keeping the notebook in a public place is
a good idea but I happen to agree with Brian that the "right place"
(IETF process wise) is IDs - for two reasons
1/ it follows our written process (which does not limit
IDs to RFC precursors)
2/ like it or not, there are easy to find archives of IDs and
that is where people look for IETF history
Scott
_______________________________________________
Ietf@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf