]> The University of Auckland

School of Computer Science The University of Auckland PB 92019 Auckland 1142 New Zealand brian.e.carpenter@gmail.com

Transport RSWG Internet-Draft This document clarifies the policy framework for changes to RFC formats and associated tool chains. About This Document Status information for this document may be found at . Discussion of this document takes place on the RSWG Working Group mailing list (), which is archived at .

Introduction The scope of work of the RFC Series Working Group (RSWG) is set by . In particular, Section 3 states that policies drafted by the RSWG "might include, but are not limited to, document formats, processes for publication and dissemination of RFCs, and overall management of the RFC Series." This definition is not explicit about the level of detail in document formats. Specifically, do technical details of the markup language, graphics formats, and internationalized character sets lie within the policy remit of RSWG, or are they the responsibility of the RFC Production Center and the IETF LLC tool support team? The purpose of the present document is to resolve this question.

Policy Considerations High level issues, such as what markup is used for documents (currently XML2RFCv3), what graphics format (current a subset of SVG), and what publication formats are used (currently plain UTF-8 text, HTML, and PDF/A) are policy matters in the purview of the RSWG, with approval by the RFC Series Approval Board (RSAB). Similarly, how to manage changes in these formats is clearly a policy matter. Technical details, for example of the XML2RFC vocabulary and of the SVG subset, need to be agreed as the result of a consensus process that includes the tools team, the RPC, and the wider community. The best existing venue for forming such a consensus is the RSWG, with approval by the RSAB. Since the RSWG was formed and announced as a policy working group, it is strongly recommended that such technical details should be developed by one or more designated RSWG design teams, as foreseen in Section 3.1.1.4 of . The resulting technical documents will be remitted to the RSWG and processed as if they were policy documents. Practical issues about the range of tools provided for authors, for readers and for the RPC's own use, and when and how such tools are implemented and updated, are operational matters in the purview of the RPC and of IETF LLC.

IANA Considerations No IANA actions are needed.

Security Considerations This document does not directly affect the security of the Internet.

Acknowledgements Useful comments were received from ...

Informative References This document specifies version 3 of the RFC Editor Model. The model defines two high-level tasks related to the RFC Series. First, policy definition is the joint responsibility of the RFC Series Working Group (RSWG), which produces policy proposals, and the RFC Series Approval Board (RSAB), which approves such proposals. Second, policy implementation is primarily the responsibility of the RFC Production Center (RPC) as contractually overseen by the IETF Administration Limited Liability Company (IETF LLC). In addition, various responsibilities of the RFC Editor function are now performed alone or in combination by the RSWG, RSAB, RPC, RFC Series Consulting Editor (RSCE), and IETF LLC. Finally, this document establishes the Editorial Stream for publication of future policy definition documents produced through the processes defined herein. This document obsoletes RFC 8728. This document updates RFCs 7841, 8729, and 8730.

Change Log [RFC Editor: please remove]

Draft-00

• Original version