[rfc-i] RSE relationship to the IAOC

Glenn Kowack glenn at riveronce.com
Mon Jan 17 23:59:00 PST 2011

Recent discussion on this list, as well as my own phone discussions, point toward
the following changes (since publication of the Overview in December) in RSE
responsibilities as they relate to the IAOC.

Two background items:
- The REOC may be constituted under the IAB's authority as defined in RFC 2850, 
	Section 2(d): ("The IAB must approve the appointment of an organization to 
	act as RFC Editor and the general policy followed by the RFC Editor.")
- The TRSE recommendations identify that the RSE requires technical (as in 
	editorial and publications techniques) and managerial expertise.

It will occasionally, be necessary to revise existing (or create new) agreements for 
contracted RFC Editor services (e.g,. the Production Center).  New contracts and 
renewals use Statements of Work (SOWs) to describe all issues related to 
contractor work performance. The RSE will lead community discussion on the 
content of SOWs.  Using that input, the RSE will revise the SOW. The RSE will
then support the IAOC in developing an RFP, with the RSE providing input related
to technical-editorial SOW content.

All RSE activities will be done with the advice and consent of the REOC, whose 
members are expected to maintain their own independent contact with the 
community (per the Overview).

The RSE will evaluate the sufficiency of bids w/r/t the SOW, and will provide input
to the IAOC. The IAOC will negotiate contract(s) with the winning bidder, with the 
support of the RSE.

If during this process the RSE does not believe his recommendations and input 
are being considered appropriately by the IAOC, then he can bring that concern
to the IAB.

The above satisfies the need for technical-editorial expertise in revising (and 
creating new) agreements while not interfering with the IAOC's execution of its
responsibilities.  The above is also consistent with BCP 101, which identifies:

	"The IASA is distinct from IETF-related technical functions, such as
	the RFC Editor, the IANA, and the IETF standards process itself.  The
	IASA has no influence on the technical decisions of the IETF or on
	the technical contents of IETF work.  Note, however, that this in no
	way prevents people who form part of the IASA from participating as
	individuals in IETF technical activities."

This email defines RSE (and REOC) expertise as technical, and thus appropriate 
as described above.


More information about the rfc-interest mailing list