[bfcpbis] Documentation conclusions

["DRAGE, Keith (Keith)" <[e-mail]>]

(As WG cochair)

We opened a discussion earlier in the year about the documentation of the 4582bis document (and what we needed to do with the 4583bis issues as well).

There was a limited response on list which went in one particular direction, and the interim meeting (today) essentially agreed with that view.

I'd therefore like to confirm that decision on list with responses requested by close of business Monday 27th February.


The decisions are:

-	To provide a complete replacement of RFC 4582 as as bis version, i.e. all the contents of RFC 4582 will be copied into the replacement document and modified to provide the enhancements.

-	To provide a short annex detailing the differences, but this will not be sufficient for implementors to work from if they are enhancing existing implementations.

-	To ensure that the diff tools (see tools.ietf.org) will work between RFC 4582 and its replacement so that implementors enhancing existing implementations will be able to identify the technical changes from the diff so created.

-	To do this as soon as the editor can work through this. The hope is that the -02 version will be in this form, along with any technical changes intitiated by the interim meeting.

-	To apply the same process to an RFC 4583 bis version (contents of which are identified in section 5 of draft-ietf-bfcpbis-01). The chairs are currently working on creating a milestone for this document. In case of time constraints the editor will give priority to the 4582bis document.


If any member of the working group has any issues with the above please reply by the deadline above to this mail.

Regards

Keith