RFC 12345 Purple Tests November 2025
Mahoney Informational [Page]
Stream:
Internet Engineering Task Force (IETF)
RFC:
12345
BCP:
999
Obsoletes:
3261
Updates:
9110
Category:
Informational
Published:
ISSN:
2070-1721
Author:
J. Mahoney, Ed.
RFC Production Center

RFC 12345

An RFC for Testing RFC Publication Using Purple

Abstract

This document is to test Purple and Red publication functionality.

It updates RFC 9110 and obsoletes RFC 3261.

It makes RFC 7991 historic.

It is a Best Current Practice.

Status of This Memo

This document is not an Internet Standards Track specification; it is published for informational purposes.

This document is a product of the Internet Engineering Task Force (IETF). It has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are candidates for any level of Internet Standard; see Section 2 of RFC 7841.

Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc12345.

▲

Table of Contents

1. Introduction

Introductory text [REPLACE]

1.1. Requirements Language

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.

2. Body [REPLACE]

Body text [REPLACE]

To use a cite tag, see [exampleRefMin] and [exampleRefOrg].

  1. Ordered list item [REPLACE/DELETE]
First term: [REPLACE/DELETE]
Definition of the first term [REPLACE/DELETE]
Second term: [REPLACE/DELETE]
Definition of the second term [REPLACE/DELETE]
Table 1
Column 1 [REPLACE]
Cell [REPLACE] 
<CODE BEGINS> file "suggested filename [REPLACE/DELETE]"


source code goes here [REPLACE]


<CODE ENDS>
Figure 1: Source [REPLACE] 
-------------
     art
-------------
Figure 2: Diagram [REPLACE]

3. IANA Considerations

This memo includes no request to IANA. [CHECK]

4. Security Considerations

This document should not affect the security of the Internet. [CHECK]

5. References

5.1. Normative References

[RFC2119]
Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/info/rfc2119>.
[RFC8174]
Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, , <https://www.rfc-editor.org/info/rfc8174>.

5.2. Informative References

[exampleRefMin]
Surname [REPLACE], Initials [REPLACE]., "Title [REPLACE]", .
[exampleRefOrg]
Organization [REPLACE], "Title [REPLACE]", , <http://www.example.com/>.

Appendix A. Appendix 1 [REPLACE/DELETE]

This becomes an Appendix [REPLACE]

Acknowledgements

This template uses extracts from templates written by Pekka Savola, Elwyn Davies and Henrik Levkowetz. [REPLACE]

Contributors

Thanks to all of the contributors. [REPLACE]

Author's Address

Jean Mahoney (editor)
RFC Production Center
URI: www.rfc-editor.org