Hi,
on 2006-07-18 17:24 IETF Administrative Director said the following:
The IAOC intends to issue an RFP for the RFC Editor function no later than 31
July 2006. To that end we seek your review and comments to the draft RFP.
I just thought of and checked up one particular issue in the SOW in
Appendix 1 of the RFP, regarding the handling of document sources.
I found that currently, the SOW doesn't require the sources to be publicly
available at all, and availability of the published document is only assured
through a search interface. The availability of RFCs in a mirrorable form
(by ftp or rsync) is not covered, it seems.
Should we require that the current availability through rsync and ftp
is continued?
If yes, should we also add a requirement for rsync and ftp availability
of the document sources?
Regards,
Henrik
--------
Details excerpted from the SOW:
Section 3 subsection a of the SOW says:
a. Indexing: Maintenance of the Catalog
...
5) Provide the permanent archive of any source documents associated
with a published specification
...
and Section 3 subsection c of the same SOW says:
c. Access to Published Documents
1) Provide search tools for finding published documents and relevant
meta information associated with a published document such as,
category of document, type of standard (if standards track),
obsoleted by or updated by information, and associated errata
2) Integrate search tools with the IETF search tools
while Section 4 only seems to cover online access to status and statistics
information:
4. Communication of relevant RFC and processing information online
The RFC Editor shall maintain a website with the following information:
a. Publication Status Tracking
...
b. Providing Publication Statistics and Status Reports
...
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf