Wanted to send an update outlining a little bit of process for how we're
going to manage the production of a 3825bis document. Because there is
a desire in the group to manage carefully the differences between this
update and RFC 3825, we'll use the following process:
1. The -00 draft will just be RFC 3825 with updated boilerplate.
2. Issues and proposed resolutions will be proposed to the list and
entered as tickets for the milestone draft-ietf-geopriv-3825bis on the
geopriv trac page:
<http://trac.tools.ietf.org/wg/geopriv/trac/report/1>
(Note: you will need an account on the tools page to do this. Let me
know if this is an issue for you.)
3. Based on discussion on the list, changes will either be added to the
document or dropped, with the corresponding result noted in trac.
Issues with widespread agreement will be added as the editor sees fit;
issues that are more contentious may require a consensus call.
I have seeded the tracker with a set of changes that were agreed to at
the virtual interim and in subsequent consensus calls.
Bernard Aboba has graciously agreed to serve as editor for this
document, and should have an initial version out soon.
Thanks,
--Richard
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv
