Internet-Draft Abbreviated Title February 2022
Bormann & Surname [REPLACE] Expires 5 August 2022 [Page]
Workgroup:
Internet Engineering Task Force
Internet-Draft:
draft-example-00
Published:
Intended Status:
Informational
Expires:
Authors:
C. Bormann
🦄
Initials [REPLACE]. Surname [REPLACE], Ed.
Organization [REPLACE/DELETE]

Title [REPLACE]

Abstract

Abstract [REPLACE]

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on 5 August 2022.

▲

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]

  1. Ordered list item [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]

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]

Authors' Addresses

Carsten Bormann
ignoredtoyota1
ignoredtoyota2
Additional contact information:
ボーマン カーステン
トヨタ自動車株式会社
トヨタ
fullname [REPLACE] (editor)
Organization [REPLACE/DELETE]
Street [REPLACE/DELETE]
City [REPLACE/DELETE]
Phone: Phone [REPLACE/DELETE]
URI: URI [REPLACE/DELETE]

mirror server hosted at Truenetwork, Russian Federation.